This printer appears to require hplip 3.9.2 or later to drive it. This
is available in the current OpenSolaris builds, but as far as I know, it
isn't built or packaged for Solaris 10. If you want to use this printer
off a Solaris 10 system, you would need to either locate a pre-built set
of
Your printer should work under CUPS + Gutenprint 5.2.4. CUPS has been
in OpenSolaris for a while now and is the default print service on a
fresh install as of build 129. Gutenprint (formerly gimpprint) was
upgraded to 5.2.4 in build 127. So your printer should work on the
current developmen
On 03/ 8/10 06:31 PM, Hillel Lubman wrote:
>> I have filed bug 6927296 and placed you on the interest list, so you
>> will be able to track this. The hplip owner will likely look at the bug
>> and add the filter to the packaging in an upcoming build.
>>
> Is it planned to include this fix in
On 02/17/10 03:57 PM, Hillel Lubman wrote:
> Norm Jacobs wrote:
>
>> I have filed bug 6927296 and placed you on the interest list, so you
>> will be able to track this. The hplip owner will likely look at the bug
>> and add the filter to the packaging in an upcoming
On 02/17/10 10:51 AM, Hillel Lubman wrote:
> As of build snv_132, a problem mentioned
> here:http://www.opensolaris.org/jive/thread.jspa?messageID=431342#431342T
> still persists. Color Laserjet 3800 can't be used with CUPS because of
> missing hpcac component. It reports:
>
> Printer [name] re
andrew wrote:
> See bug 13632 here:
>
> http://defect.opensolaris.org/bz/show_bug.cgi?id=13632
>
> If anyone has got cups working on build 130, including system-config-printer
> then I would be very interested to here about it as it's got me totally
> stumped.
>
> Cheers
>
> Andrew.
>
The bug
Eldee Stephens wrote:
> ghee, et al,
>
> with the fast approaching switch-over to CUPS as the default printing system
> in opensolaris, what is presto's future? one of the delights of working with
> opensolaris -- at least in desktop usage -- has been the zero-effort
> configuration of nearby n
Stephen Green wrote:
> Hi folks. I'm running snv_127 and using CUPS as my printing system. I've
> been having some trouble printing, so I sat down tonight to take a look at
> it. I followed the advice in:
>
> http://defect.opensolaris.org/bz/show_bug.cgi?id=12719
>
> and replaced the USB backe
HPLIP was upgraded to v3.9.8 in build 126. It sounds like there is a
regression in the hpijs functionality (at least for this printer). From
the error messages, it really looks more like some sort of overflow or
type conversion issue while processing the page size attributes from the
PPD. I
It looks like the driver that was selected doesn't match your printer.
I don't see an OpenSource driver for this model of printer anywhere.
Gutenprint is upgraded in build 127, so you might be able to try it.
-Norm
Robs wrote:
> Hi.
>
> I've got a Canon iP100 USB printer hooked-up to my Op
the remote
print server. That's why the change needs to be made to /etc/inetd.conf
on the linux print server.
-Norm
>
>
>
>
>
> Thanks & Best Regards
>
>
> -Original Message-
> From: Norm Jacobs [mailto:Norm.Jacobs at Sun.COM]
>
F?lix Ren? Salvador wrote:
> Norm,
>
> Thanks so much for your both valious help and information.
> I will proceed with your indications.
>
> However, I still have a doubt. Do I have to upgrade from 111b to 122b first?
> What do you mean with "you will want to fix for 6766216 create
> /usr/lib/cup
I will save you some trouble. There is an incompatibility between the
versions of hpijs and foomatic-rip used by LP. It's a known bug and it
will be fixed when the foomatic-filters package is upgraded to v4.0.3.
We don't have an ETA for the foomatic-filters upgrade. CUPS doesn't
have this
I'm including printing-discuss since it's probably a better forum for this.
The Window printing model differs from Solaris in that a Windows print
server pretty much expects that the client systems will supply printer
ready output, so depending on your needs, you might consider creating a
loca
Moinak Ghosh wrote:
> On Sun, Oct 11, 2009 at 7:45 AM, Arun Tomar wrote:
>
>> hi!
>>
>> i've an hp office jet all in one f4288. the printer gets detected and
>> works if i configure cups but the scanner doesn't. sane gives the error
>>
>> arun at opensolaris:~# scanimage -L
>>
>> No scanners we
Christian Thalinger wrote:
> On Sun, 2009-04-19 at 18:06 +0200, Christian Thalinger wrote:
>
>> Hi!
>>
>> I'd like to buy an All-In-One printer that works in OpenSolaris and I
>> think either the J4680 or the J6410 would be a good choice.
>>
>> There is only one thing I'm worried about: the HPLI
The desktop-print-management script should should be falling back to the
CUPS web interface if system-config-printer fails to run. If it
doesn't, it's a bug that needs to be filed.
-Norm
which would tell you that system-config-printer isn't installed (if it
isn't) and then open up the
Ghee Teo wrote:
> On 02/18/09 02:49, Halton Huo wrote:
>> On Tue, 2009-02-17 at 18:25 -0800, weknox wrote:
>>
>>> Yes. Other applications fail to print large documents too.
>>>
>>
>> Would you like file a bug on defect.opensolaris.org against
>> Development/gnome? And please attach your ex
Matthew Coffin wrote:
> Hi everyone -
>
> I want to use my Epson DX4850 with OS, but although presto detects the usb
> printer when connected, it cannot create the printer correctly, as there is
> no PPD file (am i corrrect) for this printer. searching the web, i have found
> lots of advice -
Ghee Teo wrote:
> Norm Jacobs wrote:
>> Ghee Teo wrote:
>>> Norm Jacobs wrote:
>>>
>>>>>
>>>>>> 3. Should we use the CUPS or the LP print service
>>>>>> on Solaris?
>>>>>> (sounds like C
I am going to guess that the problem you are running into is (at least
in part) due to an incompatiblity between the foomatic-rip that LP is
using and the current hpijs. You might try modifying the interface
script for your queue (/etc/lp/interfaces/{queue-name}) so that it uses
/usr/lib/cups/
Did you use the "Lexmark 4039 10plus" driver for this? Under LP? If
not, you might try that, though it's not clear to me that it will
actually generate PostScript Level 1. If that is not working you can
switch to CUPS and try to set GhostScript pre-filtering to "Convert to
PS Level 1" throug
Ghee Teo wrote:
> Norm Jacobs wrote:
>> Ghee Teo wrote:
>>> Norm Jacobs wrote:
>>>
>>>>>
>>>>>> 3. Should we use the CUPS or the LP print service
>>>>>> on Solaris?
>>>>>> (sounds like C
You are still missing libgs from GhostScript. The precompiled,
prepackaged version of GhostScript currently delivered into Solaris
doesn't include libgs so until that changes, you will have to build it
yourself. That should reduce the unresolved symbols, but I expect that
a few will remain.
Yes, the instructions I posted previously should do the trick. If not,
let me know.
-Norm
Greg Palmer wrote:
> Hi Norm,
>
> I am trying to setup a HP j6480 All in One as a network printer. It has the
> built in wireless card and also defaults to port 9100 to listen on. Would the
> s
I haven't looked at foo2zjs in a while, but the last time I built it, it
built right out of the box. You might try to set
INSTALL=/usr/bin/ginstall. eg.
env CC=gcc INSTALL=/usr/bin/ginstall gmake install
-Norm
Ingo Huber wrote:
> For opensolaris rookies - like me - how to handle this fil
Ghee Teo wrote:
> Norm Jacobs wrote:
>
>>>
>>>
>>>
>>>> 3. Should we use the CUPS or the LP print service
>>>> on Solaris?
>>>> (sounds like CUPS is going to be the preferred
>>>> print service).
Jonathan Adams wrote:
>> I would like to run a Virtual Print Server for
>> Solaris, Windows, Linux and Mac clients.
>>
>> Currently our Windows and Mac clients print directly
>> to the network printers
>> and we have no control over the print jobs that are
>> submitted.
>>
>> The plan is to move al
Ghee Teo wrote:
> niv wrote:
>
>> Hi,
>>
>> Thanks for the reply.
>>
>> There is actually seems to be 2 declarations for Printer model .
>> foomaticrip.c file has
>> char printer_model[128] = "";
>>
>> options.c has
>> char printer_model [256];
>>
>> I removed char printer_model [256]; from op
Jonathan Adams wrote:
> Hmm ... that printer doesn't seem to do PCL ...
>
> http://openprinting.org/show_printer.cgi?recnum=HP-OfficeJet_Pro_L7580
>
> http://hplipopensource.com/node/125
>
> I'm not sure if the HPLIP Linux stuff will work on OpenSolaris, but the HPIJS
> should work.
>
OpenSolar
I would suggest that you use CUPS. In your case, it probably makes more
sense than it might for some, but if you are deploying with Linux, and
MacOS, they already use CUPS and depending on your needs/network you may
want to just enable the CUPSBrowse support for advertising your printer
to ot
It sounds sort of like the usbprn(7d) driver didn't attached to the
device. It there a node for it in /dev/printers/? or /dev/usb/printer?
What does "/usr/lib/lp/bin/printer-info -a /dev/printers/*" return? I
don't have an OfficeJet 5600 series printer to test, but my C7280
attaches and wor
Dennis wrote:
> Yes, it is a USB printer HP ColorLaserjet 2605dn.
>
> I have read that there is a issue with USB printers. (6697318 printing to USB
> hands under CUPS). So I added the line "FileDevice Yes" in my cupsd.conf (Was
> this correct?) and in the /etc/cups/printers.conf I changed to line
Peter Eriksson wrote:
> I've been trying to figure out if it is possible to have Solaris print client
> support IPP authentication for users. Our university is deploying a all new
> and (. fantastic .) central print system that requires user authentication
> for printing to succeed.
Yes, the So
This is due to
6697318 printing to USB hands under CUPS
You should be able to workaround it using "file://dev/printers/0" (or 1,
2, ...) as the device URI until it gets fixed. You will need to enable
"FileDevice Yes" in your cupsd.conf to set the device to a path in the
filesystem.
-Norm
aric
Funny, someone sent my private mail a couple of days ago with almost
exactly the same "errors". The issue was that they SMF manifest hadn't
been imported yet. A reboot or "svcadm restart manifest-import" should
help you.
-Norm
You should have the SUNWcups package installed
> > opensola
Bill Shannon wrote:
> Norm Jacobs wrote:
>>
>> Bill Shannon wrote:
>>
>>> We are planning to move to CUPS, but want to integrate support for
>>> various Solaris features before we dump LP.
>>
>> Like what?
RBAC, Trusted printing, SunRay attac
Bill Shannon wrote:
> (I'm running snv_98.)
>
> While working on a printing problem, I decided to use the Print Manager
> to configure the printer.
>
> I was surprised to see the old Solaris Print Manager instead of the
> CUPS print manager that I see on Ubuntu.
>
> I saw the message from Norm ear
You should be switching print services LP <-> CUPS using print-service (1m)
# print-service -s lp
or
# print-service -s cups
This will disable/enable the appropriate services and toggle a bit in
the SMF repo that tells lp/lpstat/cancel/lpr/lpq/lprm/... which print
service is the "active" servi
I think that because of some changes in the desktop integration, you end
up with two "ospm-applet"s running. It likely that they are stepping on
each other and causing your problems. I am running OSOL_98 and able to
hotplug printers after killing off the second ospm-applet (several
times).
The bug id I supplied is in the internal bug DB. It should be visible
externally, but doesn't appear to be. I don't know why.
-Norm
John wrote:
> Thank you, adding my user name to the sys row of /etc/group fixed the
> problem. By the way, is http://defect.opensolaris.org/bz/ the addr
This appears to be related to the root account being changed to a role
in OpenSolaris. If you add yourself to the "sys" group for the time
being, you should be able to work around it., you can work around it for
the time being. This is being tracked under bug "6717444 Unable to add
printer."
If you suppy the printer make/model information and "lpstat -p queue -l
2" information for your print queue, we might be able to help you further.
-Norm
rose dawson wrote:
> Hi, I want the network printer in my computer. Sometime I have problem in my
> printer. The printing page is full
Jean-Paul Rivet wrote:
>> I've been trying to get this work but still have a
>> bit to go
>>
>> I have configured a Windows Vista client to point to
>> http://{hostname}:631/printers/epson890 and they have
>> installed the printer correctly.
>>
>> However when printing a test page, it appears
Though CUPS and LP can and do use several common pieces of software on
Solaris for printer support and SMB support, they aren't integrated with
each other. CUPS can be used in place of LP and vice versa. If you
want to switch between CUPS and LP you can use the print-serivce(1m)
command:
The output of lpstat -p HP1022 -l might be more helpful. It looks like
you have a queue, but there isn't enough to tell what "printer driver"
it's configured to use. That being said, this printer appears to
require HPLIP 2.7.10 or later or foo2zjs to work. We should be
upgrading to HPLIP 2.
I don't think that Omni is being actively developed any more. We
haven't built it or support for it in the GhostScript that ships on
Solaris. Blastwave and sunfreeware don't appear to ship it either. You
might try out the built in epl* ghostscript drivers to see if one of
them supports your
Not sure why you get 31 seconds. There is a hardcoded 15 second wait in
psm-lpd.so when it attempts to connect to a remote print service.
-Norm
Ghee Teo wrote:
> Hi,
>
> I have a queue which is to access a remote print server, but the remote
> print server has since
> been re-installed,
There is a section of the anserbook that should help
http://docs.sun.com/app/docs/doc/806-4074/6jd68ppls?l=en&a=view
If the queue is on a remote print server (host that queues and filters)
# lpadmin -p queue -s server
or
# printmgr
on menus (printer) -> (add access to printer ...)
snv_87 has a broken GhostScript (fixed in snv_88), so depending on your
printer, nothing may print in 87. As for evince not printing, I looked
at the output that it generated from a PDF file I wanted to print and
the PostScript generated claims to be Level 3. There are still plenty
of PostSc
You are probably running into
6687464 Ghostscript looks in wrong place for gs_init.ps
It's fixed in 88.
-Norm
David Burge wrote:
> When using cups or lp, foomatic-rip gets an error 29 when I try to print to
> my HP Officejet 6210. This printer continues to work fine in build 86. I
The most likely cause for this type of hang is that printing is trying
to contact a network name service like NIS or remote print service that
is down.
If you are not really sharing printing configuration via a network name
service, make sure that the "printers" entry only contains "user files"
There is a PPD file for this specific model of printer on
openprinting.org in the foomatic DB. From looking at it, it looks like
this printer should work with the HL-2060 hl1250 PPD file or
you can download the HL-2040 specific PPD and add it to your system with
ppdmgr(1m).
This is the URL you
I think that we should update the hald-probe-printer to add the printer
capability to the HAL device tree node when it gets back IEEE1284
DeviceID information for a printer. I just filed the bug.
6697336 hald-printer-probe should update capabilities too
I will try to fix it and integrate in
If your printer is plugged in and powered on when HAL starts, it should
show up in the HAL device tree, which means that the OSPM should offer
you the opportunity to create a print queue for it when you login. To
determine if hal has identified it use:
% lshal -l -u $(hal-find-by-capabili
Since you are building against the the Blastwave bits (CSW), make sure
that your resulting bits have /opt/csw/lib in their RUNPATH. Take a
look at the output of "dump -Lv (file)" for your various bits. Example
from some companion bits. note the RUNPATH.
% dump -Lv /opt/sfw/bin/gifbg
/opt/sf
I am planning on attending. I expect that I can find something to
ramble on about.
-Norm
Ghee Teo wrote:
> I noted that there is an item on OpenSolaris Printing on the link below:
>
> http://www.genunix.org/wiki/index.php/OpenSolaris_Summit
>
> Anyone on the list is giving the talk?
>
>
Late last week, I integrated CUPS 1.3.6 + updates to other printing bits
into Solaris. They will show up in Nevada build 87. I have been
running the same CUPS bits that are in build 87 on my desktop for a
month or so without any problems. SO seems to be printing fine, as do
Firefox/Thunderbi
The intention is to add this to Solaris in the next few months. While
the IJS component of HPLIP can be used with Foomatic and LP, the bulk of
HPLIP effectively requires SANE and CUPS. I am working on integrating
CUPS in the next few weeks. Someone else is working on integrating SANE.
When the
Mike Kuhnkey wrote:
> Connected EPSON Stylus PHOTO RX600 to torture 64-bit install of:
> cat /etc/release
>Solaris Express Community Edition snv_84 X86
>Copyright 2008 Sun Microsystems, Inc. All Rights Reserved.
> Use is subject to license t
FWIW, gs is in /usr/bin in Nevada.
-Norm
Benoit Heroux wrote:
> I was near the answer when i posted my last message.
>
> I changed the LogLevel on the cupsd.conf to "debug" then i test another page
> and found this:
>
>
> D [15/Mar/2008:14:01:53 +0500] [Job 19] perl: warning: Falling bac
John-Paul Drawneek wrote:
> Err I mention that is a network printer twice.
>
Most of the Presto related comments that I have received thus far are
for USB attached printers and not network attached printer discovery so
I managed to skip over that little bit of information each time I read
you
The Foomatic DB at linuxprinting.org claims that it works perfectly with
foomatic, but the PPD isn't on the site. I am curious about the PPD you
used and how you are connected to it (I assume USB based on your
comments below) The fact that the light flashes would mean that you are
generating
* You can configure it by hand using lpadmin(1m) and use the -n
option to specify the path to the PPD file.
# lpadmin -p queue -m uri -n ppd-file -v socket://printer:9100 ...
* You can configure it using the printmgr(1m), use the wrong PPD
file, and add the correct PP
My recollection was that this was the default behaviour for the tsol_*
model scripts, though it may only work for PostScript printers.
-Norm
Elijah Reed wrote:
> I asked this question in the past with no response so here we go again.
>
> I have a Solaris 10 Update 4 TX system with a print
You should be able to configure the CUPS client in the lxBrandz Centos
3.7 environment to talk to the IPP listener in the global zone. The IPP
listener implements several CUPS extensions to IPP so that CUPS clients
can use a Solaris LP based server.
From a client system (media-center) running
The linuxprinting.org foomatic printer database classifies this printer
as a "paperweight", more or less meaning that there are no known open
source drivers for this printer. The message you reference on the
ubuntuforums refers to a Lexmark linux ddk that doesn't appear to be
available from L
r.com/linux/en_us/index.html for information on
their open source drivers.
-Norm
Alok Aggarwal wrote:
>
> On Thu, 17 Jan 2008, Norm Jacobs wrote:
>
>> From the message that you are supplying, it sounds like you have your
>> system misconfigured to go directly to th
From the message that you are supplying, it sounds like you have your
system misconfigured to go directly to the printer and I don't know what
protocol (I am assuming that the printer is at 192.168.1.103). You
might try to use presto with the network attached printer detection
support now in
If you build under usr/src/lib/print/libpapi-lpd, you should only need
to replace /usr/lib/print/psm-lpd.so.1 with the copy that you built,
though it gets a little more complicated as you move backward in time
because I "fixed" the interface between psm-lpd.so.1 and lpd-port
several builds back
Glad to hear that it was detected and worked out of the box. I would
like to place one caveat on Ghee's note. The network attached printer
discovery currently only supports SNMP, so if your network attached
printer supports SNMP, it will be detected. A couple of months ago, I
saw a new netw
It looks like the option is being passed on the network using the wrong
control file extension. I have picked up the bug and will take care of
it. It will probably be in build 82
-Norm
--- usr/src/lib/print/libpapi-lpd/common/lpd-job.c ---
369c369
< add_svr4_control_line(metadata, 'o'
The FAQ at http://www.opensolaris.org/os/community/printing/faq/ should
help. If you are using a current SXDE, the printmgr(1m) should allow
you to configure a "new network printer" using the "URI" protocol and
the smb://windows-server/queue uri form for the destination.
Windows printing requir
Personally, I would love to, but the fact that it doesn't come with
licenses for for some active patents that it appears to implement is
going to be a problem.
-Norm
Ken Mandelberg wrote:
> Sorry for the noise. This went in easily in snv_77 Sparc. I saw the reference
> to i386 and didn
The instructions that Rick sent out should work on either sparc or x86.
The only change that I had was to force make to use gcc instead of the
default 'cc' C compiler.
$ gmake CC=gcc
-Norm
Ken Mandelberg wrote:
> This thread references an i386 path.
>
> I need foo2zjs support for an HP
s is to allow the various applications developers to
> be informed and involved if needed to.
>
> Norm Jacobs wrote:
>> We are looking at integrating CUPS into Solaris as a choice for
>> printing. This really means CUPS, new attendant add-on packages, and
>> enabling CUPS suppor
Comments are inline
Pascal Kreyer wrote:
> On which level will CUPS be integrated ? Between the customer
> application and the printer directly or through PAPI ?
>
> Why should we add cups support on GTK, mozilla products or staroffice if
> we send the printers through PAPI ?
>
We actually
We are looking at integrating CUPS into Solaris as a choice for
printing. This really means CUPS, new attendant add-on packages, and
enabling CUPS support in some existing packages that we ship.
1. We will ship packaging for both LP and CUPS.
2. You will be able to install LP, CUPS, or
The Make/Model don't necessarily identify a single PPD file. I was
thinking about a third pulldown menu allowing the user to choose the
specific PPD file from what the Make/Model narrow it down to.
-Norm
Ghee Teo wrote:
>
>> At least for the short term, we should probably change the OSPM "
Mark F Villa wrote:
> Norm Jacobs wrote:
>
>> The "Presto" bits use HAL and a probe program to identify new USB
>> printers when they are attached. The thing is that many printers
>> don't identify themselves as the exact model on the sticker. Often
&
ed the PPD, the commands started running, although
> printing from 'evince' isn't working
> yet.
>
> The funny thing is, when I tried this on a different (forgotten name)
> HP printer, it seemed
> to get the correct model but
>
> Anyway, this got me going
DESKJET
>cmd[5]: DYN
>
>
> me2: ~ > lpstat -p queue -l 2
> queue: unknown printer
>
>
> me2: ~ > lpstat -t
> scheduler is running
> system default printer: 8100_series
> device for 8100_series: /dev/printers/1
> 8100_series accepting requests since Th
I wouldn't expect you to get garbage when you print from FireFox to your
printer. It sounds like the wrong PPD file was associated with the
queue for your printer. What kind of printer do you have? How is the
queue configured?
If it's Parallel or USB attached
# /usr/lib/lp/bin/printer-in
I can't reproduce this. What's in
/var/lp/logs/lpsched
/var/svc/log/application-print-server:default.log
Do you have any core files from lpsched?
If you enable lpr.debug in syslogd(1m), what messages do you get?
-Norm
Marcin Wo?niak wrote:
> maybe someone had this problem with ap
Thanks for the update. I just installed the bits on my desktop. I had
to use
$ CC=gcc gmake
to build. Prior to that it was failing building in icc2ps because CC
was resorting to a default (cc) instead of what was set in the upper
level Makefile.
Can you point me at more information rega
Rick Richardson wrote:
> Hello???
>
> Anybody home??
>
Yup, we are out in the ether. To answer your question. There is a
strong desire to provide the type of access to PPD data that you are
referring to. The Presto project
(http://www.opensolaris.org/os/project/presto/) is automating print
You might be able to use GhostScript to convert everything to PS Level 1
on the way to the printer. This would require either a custom PPD file
or custom interface script.
-Norm
Gary Gendel wrote:
> I've got an old workhorse printer that still works great, a "IBM" Lexmark
> 4039 10R.
See the following bugs...
6602462 IPP listening service is broken in snv_70
6603313 dlclose() can fail to unload objects after fix for 6573641
You can get it working again by reordering
/etc/apache/httpd-standalone-ipp.conf
so that
LoadModule ipp_module libexec/mod_ipp.c
A
ime, Evince will actually print double-sided. How does one determine
> which ppd files support duplex printing?
>
> aric
>
> On Sun, 26 Aug 2007 23:48:19 -0500
> Norm Jacobs wrote:
>
>
>> Is it possible that this isn't what your snv_64b configuration looked
>> l
It sounds like it might be trying to contact a remote print server. Do
you have any remote queues configured in /etc/printers.conf or
~/.printers ? You might try turning on 'lpr.debug' in the syslog and
looking at the log, though I don't recall that there is a whole lot of
logging in the commands.
Is it possible that this isn't what your snv_64b configuration looked
like? It looks like this was configured for you by Presto. Did you get
a popup asking you to add a queue when you first logged in?
The PPD file that you have configured doesn't appear to have any options
for Duplex printing
I haven't setup MLP printing in about a year and I don't remember much
in the way of the specifics of getting the local zone to talk to in.lpd
in the global zone. You might try to connect from local zone to in.lpd
in the global zone via telnet (telnet global-zone-ip 515) just to see if
you ca
Paul Cunningham wrote:
> Minor comment ...
>
> usr/src/tools/install-proto
> line 149
>- the 'chown; is commented out, doesn't that make the rest
> of the 'if' statement (143 to 150) redundant?
Thanks. I will fix it.
-Norm
The last I
> tried to compile, I got into some problem with the forte compiler.
> Thanks,
>
> -Ghee
>
> Paul Cunningham wrote:
>>
>>
>> Norm Jacobs wrote:
>>> FWIW, you should be able to download it, build it and install it
>>> with
FWIW, you should be able to download it, build it and install it with
very little effort. If you run into problems, let me know. I managed
to get a Minolta-QMS Magicolor 2300DL working from Solaris with it.
-Norm
M Pavan Kumar Reddy wrote:
> Thank you very much for the information Wend
und build 44.
-Norm
> Thanks again
> Maurice
>
> -Original Message-
> From: Norm Jacobs [mailto:Norm.Jacobs at Sun.COM]
> Sent: Monday, May 14, 2007 2:51 PM
> To: Maurice Jeter
> Cc: printing-discuss at opensolaris.org
> Subject: Re: [printing-discuss] Printing
The behavior you are seeing sounds like a bug in lpsched, but I don't
know that I have enough information to be certain.
You might turn on the syslogd(1m) lpr.debug logging and take a look at
it. lpsched and some of the interface scripts log several key events
and bits of information that shoul
Sorry for the duplicate, I didn't see this on printing-discuss for some
reason and replied privately. I am resending to cc the list in case
others are interested.
The problem is that the IPP listener only interacts with local print
queues in Solaris 10. Your print queue configuration has prin
As long as the print server is offering rfc1179 service for the named
queues, it shouldn't matter what it's running (more or less,
non-bsd-ish/non-svr4-ish query output would be a problem). The fact
that you aren't getting any messages after disabling lpsched is
disturbing. lpstat -p should
lpstat/libpapi.so doesn't attempt to contact a local print service
unless it runs across printers(4)/printers.conf(4) configuration that
tells it there is a local queue. I'm not sure what's going on here,
turn on lpr.debug in the syslog and send the info.
-Norm
From my Nevada build 63 la
1 - 100 of 151 matches
Mail list logo
