On 20.02.2015 16:52, Tim Waugh wrote:
> On Fri, 2015-02-20 at 14:38 +0100, poma wrote:
>> https://admin.fedoraproject.org/updates/system-config-printer-1.5.5-2.fc21
>> ...
>> bodhi - 2015-02-16 09:09:19
>> This update has reached 7 days in testing and can be pushed to stable now if
>> the maintai
On Fri, 2015-02-20 at 14:38 +0100, poma wrote:
> https://admin.fedoraproject.org/updates/system-config-printer-1.5.5-2.fc21
> ...
> bodhi - 2015-02-16 09:09:19
> This update has reached 7 days in testing and can be pushed to stable now if
> the maintainer wishes
>
> This should be a karmathemati
https://admin.fedoraproject.org/updates/system-config-printer-1.5.5-2.fc21
...
bodhi - 2015-02-16 09:09:19
This update has reached 7 days in testing and can be pushed to stable now if
the maintainer wishes
This should be a karmathematics? :)
+ raveit65
+ cicku
+ lnie
+ yuwata
= 4
Karma: 2
-
On 07.02.2015 23:52, Tim Waugh wrote:
> On Sat, 2015-02-07 at 13:02 +0100, Thomas Woerner wrote:
>> For now I do not have a solution besides adding a requirement for
>> python3-firewall to system-config-printer. The impact might be small
>> enough with these requirements of python3-firewall:
>
>
On Sat, 2015-02-07 at 13:02 +0100, Thomas Woerner wrote:
> For now I do not have a solution besides adding a requirement for
> python3-firewall to system-config-printer. The impact might be small
> enough with these requirements of python3-firewall:
Yes, that doesn't look too bad. I'll include t
On 02/06/2015 11:47 PM, poma wrote:
On 06.02.2015 14:05, Thomas Woerner wrote:
On 02/05/2015 06:57 PM, poma wrote:
On 04.02.2015 20:08, poma wrote:
On 03.02.2015 18:15, poma wrote:
On 03.02.2015 11:07, Thomas Woerner wrote:
On 02/02/2015 05:55 PM, poma wrote:
On 02.02.2015 17:49, poma wrote
On 06.02.2015 14:05, Thomas Woerner wrote:
> On 02/05/2015 06:57 PM, poma wrote:
>> On 04.02.2015 20:08, poma wrote:
>>> On 03.02.2015 18:15, poma wrote:
On 03.02.2015 11:07, Thomas Woerner wrote:
> On 02/02/2015 05:55 PM, poma wrote:
>> On 02.02.2015 17:49, poma wrote:
>>> On 02.0
On 02/05/2015 06:57 PM, poma wrote:
On 04.02.2015 20:08, poma wrote:
On 03.02.2015 18:15, poma wrote:
On 03.02.2015 11:07, Thomas Woerner wrote:
On 02/02/2015 05:55 PM, poma wrote:
On 02.02.2015 17:49, poma wrote:
On 02.02.2015 17:36, Tim Waugh wrote:
On Mon, 2015-02-02 at 17:32 +0100, poma
On 04.02.2015 20:08, poma wrote:
> On 03.02.2015 18:15, poma wrote:
>> On 03.02.2015 11:07, Thomas Woerner wrote:
>>> On 02/02/2015 05:55 PM, poma wrote:
On 02.02.2015 17:49, poma wrote:
> On 02.02.2015 17:36, Tim Waugh wrote:
>> On Mon, 2015-02-02 at 17:32 +0100, poma wrote:
>>> c
On 03.02.2015 18:15, poma wrote:
> On 03.02.2015 11:07, Thomas Woerner wrote:
>> On 02/02/2015 05:55 PM, poma wrote:
>>> On 02.02.2015 17:49, poma wrote:
On 02.02.2015 17:36, Tim Waugh wrote:
> On Mon, 2015-02-02 at 17:32 +0100, poma wrote:
>> can this mechanism be improved in the way
On 03.02.2015 11:07, Thomas Woerner wrote:
> On 02/02/2015 05:55 PM, poma wrote:
>> On 02.02.2015 17:49, poma wrote:
>>> On 02.02.2015 17:36, Tim Waugh wrote:
On Mon, 2015-02-02 at 17:32 +0100, poma wrote:
> can this mechanism be improved in the way when you chose not to want
> to shar
On 02/02/2015 05:55 PM, poma wrote:
On 02.02.2015 17:49, poma wrote:
On 02.02.2015 17:36, Tim Waugh wrote:
On Mon, 2015-02-02 at 17:32 +0100, poma wrote:
can this mechanism be improved in the way when you chose not to want
to share the printer that the relevant port is closed?
Is there a san
poma ha scrito il 02/02/2015 alle 17:55:
On 02.02.2015 17:49, poma wrote:
On 02.02.2015 17:36, Tim Waugh wrote:
On Mon, 2015-02-02 at 17:32 +0100, poma wrote:
can this mechanism be improved in the way when you chose not to want
to share the printer that the relevant port is closed?
Is there
On 02.02.2015 17:49, poma wrote:
> On 02.02.2015 17:36, Tim Waugh wrote:
>> On Mon, 2015-02-02 at 17:32 +0100, poma wrote:
>>> can this mechanism be improved in the way when you chose not to want
>>> to share the printer that the relevant port is closed?
>>
>> Is there a sane way of doing that thou
On 02.02.2015 17:36, Tim Waugh wrote:
> On Mon, 2015-02-02 at 17:32 +0100, poma wrote:
>> can this mechanism be improved in the way when you chose not to want
>> to share the printer that the relevant port is closed?
>
> Is there a sane way of doing that though? I think applications wanting
> to '
On Mon, 2015-02-02 at 17:32 +0100, poma wrote:
> can this mechanism be improved in the way when you chose not to want
> to share the printer that the relevant port is closed?
Is there a sane way of doing that though? I think applications wanting
to 'reset' ports for a zone would need to know what
On 02.02.2015 14:41, Thomas Woerner wrote:
> On 02/02/2015 02:39 PM, poma wrote:
>> On 02.02.2015 12:41, Tim Waugh wrote:
>>> On Sun, 2015-02-01 at 20:28 +0100, poma wrote:
Mister Waugh,
whether it's worth a try latest and greatest?
https://git.fedorahosted.org/cgit/system-config-pri
On 02/02/2015 02:39 PM, poma wrote:
On 02.02.2015 12:41, Tim Waugh wrote:
On Sun, 2015-02-01 at 20:28 +0100, poma wrote:
Mister Waugh,
whether it's worth a try latest and greatest?
https://git.fedorahosted.org/cgit/system-config-printer.git/
The problem is that firewalld only provides Python2
On 02.02.2015 12:41, Tim Waugh wrote:
> On Sun, 2015-02-01 at 20:28 +0100, poma wrote:
>> Mister Waugh,
>> whether it's worth a try latest and greatest?
>> https://git.fedorahosted.org/cgit/system-config-printer.git/
>
> The problem is that firewalld only provides Python2 bindings, whereas
> syste
On Sun, 2015-02-01 at 20:28 +0100, poma wrote:
> Mister Waugh,
> whether it's worth a try latest and greatest?
> https://git.fedorahosted.org/cgit/system-config-printer.git/
The problem is that firewalld only provides Python2 bindings, whereas
system-config-printer is Python3.
Tim.
*/
signatur
On 02.02.2015 05:02, Chris Murphy wrote:
> On Sun, Feb 1, 2015 at 3:22 PM, poma wrote:
>> On 01.02.2015 21:41, Chris Murphy wrote:
>>> On Sun, Feb 1, 2015 at 12:28 PM, poma wrote:
On 01.02.2015 18:50, antonio wrote:
>>>
> correct, it was working in F20, but only if you were installing a
On 01.02.2015 20:28, poma wrote:
> On 01.02.2015 18:50, antonio wrote:
>> poma ha scrito il 01/02/2015 alle 18:37:
>>> On 01.02.2015 17:23, antonio wrote:
antonio ha scrito il 01/02/2015 alle 12:08:
> I was able to print from any remote computer in F20, now when I try to
> print I get
Chris Murphy ha scrito il 02/02/2015 alle 05:02:
On Sun, Feb 1, 2015 at 3:22 PM, poma wrote:
On 01.02.2015 21:41, Chris Murphy wrote:
On Sun, Feb 1, 2015 at 12:28 PM, poma wrote:
On 01.02.2015 18:50, antonio wrote:
correct, it was working in F20, but only if you were installing a new
prin
On Sun, Feb 1, 2015 at 3:22 PM, poma wrote:
> On 01.02.2015 21:41, Chris Murphy wrote:
>> On Sun, Feb 1, 2015 at 12:28 PM, poma wrote:
>>> On 01.02.2015 18:50, antonio wrote:
>>
correct, it was working in F20, but only if you were installing a new
printer, if you had already set a print
On 01.02.2015 21:41, Chris Murphy wrote:
> On Sun, Feb 1, 2015 at 12:28 PM, poma wrote:
>> On 01.02.2015 18:50, antonio wrote:
>
>>> correct, it was working in F20, but only if you were installing a new
>>> printer, if you had already set a printer (as in my case) from F19, you
>>> had to adjust
On Sun, Feb 1, 2015 at 12:28 PM, poma wrote:
> On 01.02.2015 18:50, antonio wrote:
>> correct, it was working in F20, but only if you were installing a new
>> printer, if you had already set a printer (as in my case) from F19, you
>> had to adjust by hand the Firewalld settings
>>
>
> I just chec
On 01.02.2015 18:50, antonio wrote:
> poma ha scrito il 01/02/2015 alle 18:37:
>> On 01.02.2015 17:23, antonio wrote:
>>> antonio ha scrito il 01/02/2015 alle 12:08:
I was able to print from any remote computer in F20, now when I try to
print I get socket not connected.I deleted and re-in
poma ha scrito il 01/02/2015 alle 18:37:
On 01.02.2015 17:23, antonio wrote:
antonio ha scrito il 01/02/2015 alle 12:08:
I was able to print from any remote computer in F20, now when I try to
print I get socket not connected.I deleted and re-installed remote
printer but when I try to print a te
On 01.02.2015 17:23, antonio wrote:
> antonio ha scrito il 01/02/2015 alle 12:08:
>> I was able to print from any remote computer in F20, now when I try to
>> print I get socket not connected.I deleted and re-installed remote
>> printer but when I try to print a test page it says that printer is no
Chris Murphy ha scrito il 01/02/2015 alle 17:46:
On Sun, Feb 1, 2015 at 9:23 AM, antonio wrote:
antonio ha scrito il 01/02/2015 alle 12:08:
it seems that the soultion is to check ipp and ipp-client in Firewall zones,
not so obvious when you have done a standard installation of
Fedora-Worksta
On Sun, Feb 1, 2015 at 9:23 AM, antonio wrote:
> antonio ha scrito il 01/02/2015 alle 12:08:
> it seems that the soultion is to check ipp and ipp-client in Firewall zones,
> not so obvious when you have done a standard installation of
> Fedora-Workstation (or in my case un upgrade of F20 where ev
antonio ha scrito il 01/02/2015 alle 12:08:
I was able to print from any remote computer in F20, now when I try to
print I get socket not connected.I deleted and re-installed remote
printer but when I try to print a test page it says that printer is not
connected.
Network printing is a nightmare
I was able to print from any remote computer in F20, now when I try to
print I get socket not connected.I deleted and re-installed remote
printer but when I try to print a test page it says that printer is not
connected.
Network printing is a nightmare for me, sorry to say...
--
Antonio M
Skype
33 matches
Mail list logo