On Fri, Nov 25, 2011 at 7:24 PM, Jim wrote:
> This is weird Mike , if I open Firefox and type in 192.168.0.5, IP to
> printer it shows a Information page
> from there I can PRINT out reports of the printer from that page.
> But I can't print out anything like a txt doc or Print Test Page.
> I st
On 11/25/2011 11:12 AM, mike cloaked wrote:
> On Fri, Nov 25, 2011 at 4:17 AM, Jim wrote:
>> On 11/23/2011 04:23 PM, mike cloaked wrote:
>>
>> /usr/lib/cups/filter/ a
>>
>> usr/lib/cups/filter/ has the rastertosamsungsplc and rastertosamsungspl in
>> it and permissions are the same as other exec
On Fri, Nov 25, 2011 at 4:17 AM, Jim wrote:
> On 11/23/2011 04:23 PM, mike cloaked wrote:
>
> /usr/lib/cups/filter/ a
>
> usr/lib/cups/filter/ has the rastertosamsungsplc and rastertosamsungspl in
> it and permissions are the same as other execute files.
>
>
> /usr/share/cups/model/foomatic-db-pp
On 11/23/2011 04:23 PM, mike cloaked wrote:
/usr/lib/cups/filter/ a
usr/lib/cups/filter/ has the rastertosamsungsplc and rastertosamsungspl in
it and permissions are the same as other execute files.
/usr/share/cups/model/foomatic-db-ppds/Samsung/ I put the
CLX3170splc.ppd.gz (driver for
On Thu, Nov 24, 2011 at 5:09 PM, mike cloaked wrote:
> It is hard to proceed just on the basis of the lines in the log
> if you can't remember the steps you took then you could remove the
> printer definition - and copy the two files into your system as I
> described in a previous posting. On
On Wed, Nov 23, 2011 at 10:14 PM, Jim wrote:
> ov 23 17:05:35 BigOne dbus[915]: [system] Activating service
> name='org.opensuse.CupsPkHelper.Mechanism' (using servicehelper)
> Nov 23 17:05:35 BigOne dbus-daemon[915]: dbus[915]: [system] Activating
> service name='org.opensuse.CupsPkHelper.Mechan
On 11/23/2011 02:47 PM, mike cloaked wrote:
> On Wed, Nov 23, 2011 at 5:23 PM, Jim wrote:
>> On 11/23/2011 09:34 AM, mike cloaked wrote:
>>> On Tue, Nov 22, 2011 at 12:17 PM, Jimwrote:
>>>
> I can't tell from the messages output you posted if your machine is
> x86_64 or not but I had a
On Wed, Nov 23, 2011 at 8:41 PM, Jim wrote:
> On 11/23/2011 12:23 PM, Jim wrote:
>> On 11/23/2011 09:34 AM, mike cloaked wrote:
>>> On Tue, Nov 22, 2011 at 12:17 PM, Jim wrote:
>>>
> I can't tell from the messages output you posted if your machine is
> x86_64 or not but I had a very very
On 11/23/2011 12:23 PM, Jim wrote:
> On 11/23/2011 09:34 AM, mike cloaked wrote:
>> On Tue, Nov 22, 2011 at 12:17 PM, Jim wrote:
>>
I can't tell from the messages output you posted if your machine is
x86_64 or not but I had a very very similar issue with a Samsung
scx4500w when I in
On Wed, Nov 23, 2011 at 5:23 PM, Jim wrote:
> On 11/23/2011 09:34 AM, mike cloaked wrote:
>> On Tue, Nov 22, 2011 at 12:17 PM, Jim wrote:
>>
I can't tell from the messages output you posted if your machine is
x86_64 or not but I had a very very similar issue with a Samsung
scx4500w
On 11/23/2011 11:50 AM, Jim wrote:
> On 11/23/2011 12:31 PM, Kevin Martin wrote:
>> On 11/23/2011 11:23 AM, Jim wrote:
>>> On 11/23/2011 09:34 AM, mike cloaked wrote:
On Tue, Nov 22, 2011 at 12:17 PM, Jim wrote:
>> I can't tell from the messages output you posted if your machine i
On 11/23/2011 12:31 PM, Kevin Martin wrote:
>
> On 11/23/2011 11:23 AM, Jim wrote:
>> On 11/23/2011 09:34 AM, mike cloaked wrote:
>>> On Tue, Nov 22, 2011 at 12:17 PM, Jim wrote:
>>>
> I can't tell from the messages output you posted if your machine is
> x86_64 or not but I had a very ver
On 11/23/2011 11:23 AM, Jim wrote:
> On 11/23/2011 09:34 AM, mike cloaked wrote:
>> On Tue, Nov 22, 2011 at 12:17 PM, Jim wrote:
>>
I can't tell from the messages output you posted if your machine is
x86_64 or not but I had a very very similar issue with a Samsung
scx4500w when I
On 11/23/2011 09:34 AM, mike cloaked wrote:
> On Tue, Nov 22, 2011 at 12:17 PM, Jim wrote:
>
>>> I can't tell from the messages output you posted if your machine is
>>> x86_64 or not but I had a very very similar issue with a Samsung
>>> scx4500w when I installed f16.
>>>
>>> It turned out that th
On Tue, Nov 22, 2011 at 12:17 PM, Jim wrote:
>> I can't tell from the messages output you posted if your machine is
>> x86_64 or not but I had a very very similar issue with a Samsung
>> scx4500w when I installed f16.
>>
>> It turned out that the copy of the file "rastertosamsungspl" was a 32
>>
On 11/22/2011 03:36 AM, mike cloaked wrote:
> On Mon, Nov 21, 2011 at 9:59 PM, Jim wrote:
>> Fedora 16
>> Printer has been working fine in Fedora 14, 15.
>> F16 doesn't like it.
>> I'am not getting any Selinux errors.
>>
>>
>> Printer state:
>> Idle - /usr/lib/cups/filter/rastertosamsungsplc faile
On Mon, Nov 21, 2011 at 9:59 PM, Jim wrote:
> Fedora 16
> Printer has been working fine in Fedora 14, 15.
> F16 doesn't like it.
> I'am not getting any Selinux errors.
>
>
> Printer state:
> Idle - /usr/lib/cups/filter/rastertosamsungsplc failed
>
I can't tell from the messages output you posted
Fedora 16
Printer has been working fine in Fedora 14, 15.
F16 doesn't like it.
I'am not getting any Selinux errors.
Printer state:
Idle - /usr/lib/cups/filter/rastertosamsungsplc failed
/var/log/messages
Nov 21 16:51:48 BigOne kernel: [ 1582.570767] rastertosamsung[13644]
general protectio
18 matches
Mail list logo
