From jhein at timing.com Mon Nov 1 14:56:59 2004 From: jhein at timing.com (John E Hein) Date: Tue Nov 2 07:34:10 2004 Subject: [Xprint] printing PCL Message-ID: <16774.45355.730784.356124@gromit.timing.com> x.org 6.8.1 I copied the HPLJ4050-PS model configuration to HPLJ4050-PCL5 and changed instances of "POSTSCRIPT 2" to "PCL 5". When I start Xprt, I get: No matching visual for __GLcontextMode with visual class = 1 (32774), nplanes = 8 No matching visual for __GLcontextMode with visual class = 2 (32773), nplanes = 8 No matching visual for __GLcontextMode with visual class = 4 (32770), nplanes = 8 No matching visual for __GLcontextMode with visual class = 4 (32770), nplanes = 8 No matching visual for __GLcontextMode with visual class = 4 (32770), nplanes = 8 No matching visual for __GLcontextMode with visual class = 4 (32770), nplanes = 8 No matching visual for __GLcontextMode with visual class = 5 (32771), nplanes = 8 No matching visual for __GLcontextMode with visual class = 5 (32771), nplanes = 8 No matching visual for __GLcontextMode with visual class = 5 (32771), nplanes = 8 No matching visual for __GLcontextMode with visual class = 5 (32771), nplanes = 8 No matching visual for __GLcontextMode with visual class = 0 (32775), nplanes = 8 When I try to print (xphelloworld), I get: xphelloworld: Error: no DPI set (or no default DPI provided by server) while trying to print. Is printing to PCL supposed to be working? From simon.toedt at gmail.com Fri Nov 5 16:32:30 2004 From: simon.toedt at gmail.com (Simon Toedt) Date: Fri Nov 5 10:33:20 2004 Subject: [Xprint] Xlib: extension "GLX" missing on display "simon4:50.0" while printing Message-ID: <9a9b8bd304110507325e55e2ed@mail.gmail.com> Hello, After adding a print support to our application I am getting the following warning from our application before it crashes (XPSERVERLIST=simon:50 ./wasp_core) probing loading 3D environment loading plugins... flash. . . x print Xlib: extension "GLX" missing on display "simon4:50.0". ./wasp_core: Error: couldn't get an RGB, Double-buffered visual. evey time I run the application. What does this mean and what must i do to get rid of it. I am using the GISWxprintglue package on Solaris 8 with all the newest set of patches from Sunsolve. Simon From ted at cypress.com Fri Nov 5 10:24:24 2004 From: ted at cypress.com (Thomas Dodd) Date: Fri Nov 5 11:25:30 2004 Subject: [Xprint] Xlib: extension "GLX" missing on display "simon4:50.0" while printing In-Reply-To: <9a9b8bd304110507325e55e2ed@mail.gmail.com> References: <9a9b8bd304110507325e55e2ed@mail.gmail.com> Message-ID: <418BA938.5050400@cypress.com> Simon Toedt wrote: > Xlib: extension "GLX" missing on display "simon4:50.0". > ./wasp_core: Error: couldn't get an RGB, Double-buffered visual. Looks like Xprint doesn't support GLX extensions. Compare the outputs from 'xdpyinfo -display $DISPLAY' and 'xdpyinfo -display simon4:50' to get an Idea of what Xprint doesn't support. -Thomas From dvschweiger at web.de Fri Nov 5 23:02:12 2004 From: dvschweiger at web.de (David Schweiger) Date: Fri Nov 5 17:03:14 2004 Subject: [Xprint] Xlib: extension "GLX" missing on display "simon4:50.0" while printing Message-ID: <552659727@web.de> Simon Toedt , xprint@mozdev.org schrieb am 05.11.04 16:40:35: > > Hello, > > After adding a print support to our application I am getting the > following warning from our application before it crashes > > (XPSERVERLIST=simon:50 ./wasp_core) > probing > loading 3D environment > loading plugins... > flash. . . x > print > Xlib: extension "GLX" missing on display "simon4:50.0". > ./wasp_core: Error: couldn't get an RGB, Double-buffered visual. > > evey time I run the application. What does this mean and what must i > do to get rid of it. I am using the GISWxprintglue package on Solaris > 8 with all the newest set of patches from Sunsolve. Did you install the OpenGL packages? Sun distributes their OpenGL/GLX extension separately from Solaris, by default their Xservers do not offer the GLX extension. I think you have to download and install the packages from http://wwws.sun.com/software/graphics/opengl/download.html plus the OpenGL 1.3 patches from sunsolve. __________________________________________________________ Mit WEB.DE FreePhone mit hoechster Qualitaet ab 0 Ct./Min. weltweit telefonieren! http://freephone.web.de/?mc=021201 From simon.toedt at gmail.com Tue Nov 9 02:55:55 2004 From: simon.toedt at gmail.com (Simon Toedt) Date: Mon Nov 8 20:57:02 2004 Subject: [Xprint] Xlib: extension "GLX" missing on display "simon4:50.0" while printing In-Reply-To: <552659727@web.de> References: <552659727@web.de> Message-ID: <9a9b8bd30411081755e38ec58@mail.gmail.com> On Fri, 05 Nov 2004 23:02:12 +0200, David Schweiger wrote: > Simon Toedt , xprint@mozdev.org schrieb am 05.11.04 16:40:35: > > > > > > Hello, > > > > After adding a print support to our application I am getting the > > following warning from our application before it crashes > > > > (XPSERVERLIST=simon:50 ./wasp_core) > > probing > > loading 3D environment > > loading plugins... > > flash. . . x > > print > > Xlib: extension "GLX" missing on display "simon4:50.0". > > ./wasp_core: Error: couldn't get an RGB, Double-buffered visual. > > > > evey time I run the application. What does this mean and what must i > > do to get rid of it. I am using the GISWxprintglue package on Solaris > > 8 with all the newest set of patches from Sunsolve. > > Did you install the OpenGL packages? Sun distributes their OpenGL/GLX extension separately from Solaris, by default their Xservers do not offer the GLX extension. I think you have to download and install the packages from http://wwws.sun.com/software/graphics/opengl/download.html plus the OpenGL 1.3 patches from sunsolve. That is what we tried. We even removed the installed GL packages, installed them again and added all the GL patches from sunsolve. Xsun has the GLX extension but Xprt still does not offer this extension. Simon From simon.toedt at gmail.com Tue Nov 9 02:58:32 2004 From: simon.toedt at gmail.com (Simon Toedt) Date: Mon Nov 8 20:59:46 2004 Subject: [Xprint] Xlib: extension "GLX" missing on display "simon4:50.0" while printing In-Reply-To: <418BA938.5050400@cypress.com> References: <9a9b8bd304110507325e55e2ed@mail.gmail.com> <418BA938.5050400@cypress.com> Message-ID: <9a9b8bd304110817588f1fbe7@mail.gmail.com> On Fri, 05 Nov 2004 10:24:24 -0600, Thomas Dodd wrote: > Simon Toedt wrote: > > Xlib: extension "GLX" missing on display "simon4:50.0". > > ./wasp_core: Error: couldn't get an RGB, Double-buffered visual. > > Looks like Xprint doesn't support GLX extensions. The Linux Xprt supports GLX - but we need to get it working on Solaris. Simon From julien.lafon at gmail.com Tue Nov 9 11:11:26 2004 From: julien.lafon at gmail.com (Julien Lafon) Date: Tue Nov 9 05:11:58 2004 Subject: [Xprint] [ANN]Mozilla/Firefix: New options in print job properties dialog Message-ID: ANN: Mozilla, Firefox and Thunderbird got a bunch of new options with https://bugzilla.mozilla.org/show_bug.cgi?id=262287 New options are: - Resolution, solving the permanent complaints about mis-set resolution - Colorspace, now allows to select any visual supported by the X print server (support for CYMK, YUV, etc. is planned with the X11 COLORSPACE extension) - Enable/disable font download - Job title, set alternate job title The patch also fixes the problem that certain chars (such as quotes in mail or news article subjects) corrupted the Xprint-internal resource database, causing job spooling failures. I've attached a screenshot to this mail. Feedback very welcome. -- Julien Lafon Consultant Software Engineer -------------- next part -------------- A non-text attachment was scrubbed... Name: moznewjoboptions.jpg Type: image/jpeg Size: 142824 bytes Desc: not available Url : http://mozdev.org/pipermail/xprint/attachments/20041109/a967c691/moznewjoboptions-0001.jpg From julien.lafon at gmail.com Tue Nov 9 11:18:31 2004 From: julien.lafon at gmail.com (Julien Lafon) Date: Tue Nov 9 05:19:00 2004 Subject: [Xprint] Xlib: extension "GLX" missing on display "simon4:50.0" while printing In-Reply-To: <9a9b8bd304110817588f1fbe7@mail.gmail.com> References: <9a9b8bd304110507325e55e2ed@mail.gmail.com> <418BA938.5050400@cypress.com> <9a9b8bd304110817588f1fbe7@mail.gmail.com> Message-ID: On Tue, 9 Nov 2004 02:58:32 +0100, Simon Toedt wrote: > On Fri, 05 Nov 2004 10:24:24 -0600, Thomas Dodd wrote: > > Simon Toedt wrote: > > > Xlib: extension "GLX" missing on display "simon4:50.0". > > > ./wasp_core: Error: couldn't get an RGB, Double-buffered visual. > > > > Looks like Xprint doesn't support GLX extensions. > > The Linux Xprt supports GLX - but we need to get it working on Solaris. I am not sure whether the Xprt server from Sun supports the GLX extension already or not. The feature is new in X11R6.8 (Sun ships the X11R6.8 Xorg server on Solaris 10 x86 [http://blogs.sun.com/roller/page/tpenta/20041026#solaris_express_10_04_is], if you are lucky they updated Xprt in the same step). Maybe someone from Sun can clarify the situation, please? -- Julien Lafon Consultant Software Engineer From Alan.Coopersmith at Sun.COM Tue Nov 9 07:42:08 2004 From: Alan.Coopersmith at Sun.COM (Alan Coopersmith) Date: Wed Nov 10 12:24:56 2004 Subject: [Xprint] Xlib: extension "GLX" missing on display "simon4:50.0" while printing In-Reply-To: References: <9a9b8bd304110507325e55e2ed@mail.gmail.com> <418BA938.5050400@cypress.com> <9a9b8bd304110817588f1fbe7@mail.gmail.com> Message-ID: <4190E550.6050307@sun.com> Julien Lafon wrote: > On Tue, 9 Nov 2004 02:58:32 +0100, Simon Toedt wrote: > >>On Fri, 05 Nov 2004 10:24:24 -0600, Thomas Dodd wrote: >> >>>Simon Toedt wrote: >>> >>>>Xlib: extension "GLX" missing on display "simon4:50.0". >>>>./wasp_core: Error: couldn't get an RGB, Double-buffered visual. >>> >>>Looks like Xprint doesn't support GLX extensions. >> >>The Linux Xprt supports GLX - but we need to get it working on Solaris. > > > I am not sure whether the Xprt server from Sun supports the GLX > extension already or not. The feature is new in X11R6.8 (Sun ships the > X11R6.8 Xorg server on Solaris 10 x86 > [http://blogs.sun.com/roller/page/tpenta/20041026#solaris_express_10_04_is], > if you are lucky they updated Xprt in the same step). Maybe someone > from Sun can clarify the situation, please? > I don't think we've ever supported GLX in Xprt. As for Solaris 10 x86, we only added new binaries from the Xorg tree - a later project will work on migrating existing programs such as Xprt to the new tree. If you want Xprt with GLX on Solaris now, your best bet is building your own from the Xorg tree. -- -Alan Coopersmith- alan.coopersmith@sun.com Sun Microsystems, Inc. - X Window System Engineering From roland.mainz at nrubsig.org Wed Nov 10 05:10:20 2004 From: roland.mainz at nrubsig.org (Roland Mainz) Date: Wed Nov 10 12:49:56 2004 Subject: [Xprint] [Fwd: cfb conversion effort (was Re: Debugging X.org drivers?)] Message-ID: <419194AC.7A5A6117@nrubsig.org> Hi! ---- I found the email which said that fb doesn't support some GC operation overiding... -- snip -- Intermediate challenge would be something like sunleo or sunffb, where magic GC handling is used to implement primitive acceleration - [...] This is pretty gross and fb doesn't expose the same functionality; -- snip -- ... I didn't checked that in detail but it sounds like there would be a huge problem with converting the PCL drivers from cfb over to fb (or not... I didn't investigate that in detail yet... right now I stil don't dare to touch the PCL drivers in the hope that HP will contribute their drivers back to Xorg (changing the Xorg drivers may make the merging of the HP versions more difficult)) ... ;-( -------- Original Message -------- Subject: cfb conversion effort (was Re: Debugging X.org drivers?) Date: Sun, 31 Oct 2004 02:07:14 -0400 From: Adam Jackson To: xorg@freedesktop.org CC: Roland Mainz ,Jim Gettys References: <41826D75.906.4AEE501E@localhost> <200410301759.49970.ajax@nwnk.net> <418466A8.8AE9401F@nrubsig.org> On Sunday 31 October 2004 00:14, Roland Mainz wrote: > Adam Jackson wrote: > > Kendall, I'm for some reason thinking that the SciTech drivers were based > > on the cfb framebuffer core. cfb will not work under dlloader with 6.8 > > without a patch: > > > > http://freedesktop.org/bugzilla/show_bug.cgi?id=1114 > > > > but you may be better off switching to fb. > > Do you have any example patch which shows how to turn a driver from cfb > over to fb ? HP's PCL drivers use cfb extensively and it may be nice to > switch them over, too... Sure. One trivial example is the RealVNC conversion patch Kristian H?gsberg did: http://www.mail-archive.com/vnc-list@realvnc.com/msg14387.html For drivers that treat the fb layer as something of a black box, this is all you need to do. Most of the xfree86 ddx drivers are of this sort. Until fairly recently there was still optional cfb support in six of the drivers, and http://freedesktop.org/bugzilla/show_bug.cgi?id=1192 shows the changes I made to drop that support. In all but s3virge this support was disabled at compile time, and in s3virge the cfb code was slower and, as with cfb in general, didn't support Render (and therefore Composite). Intermediate challenge would be something like sunleo or sunffb, where magic GC handling is used to implement primitive acceleration - double entendre on "primitive" totally intended. This is pretty gross and fb doesn't expose the same functionality; I suspect it can be dropped in most cases without too much pain. There's an experimental patch to convert sunleo to fb: http://freedesktop.org/bugzilla/show_bug.cgi?id=1259 which I have received no feedback on as of yet, and I don't have the hardware to verify it. sunffb is left as an exercise for the reader. The final step would be converting our overlay support to use fb. I don't even know where to begin here, largely for lack of hardware. I see a couple of functions in the fb layer that look like they're intended for overlay support. I've been tempted to just drop our overlay support altogether to see who complains; my guess is, roughly, nobody. - ajax -------------- next part -------------- A non-text attachment was scrubbed... Name: nsmail4191923701335EA Type: application/pgp-signature Size: 189 bytes Desc: not available Url : http://mozdev.org/pipermail/xprint/attachments/20041110/ef3281a7/nsmail4191923701335EA.bin From Alan.Coopersmith at Sun.COM Wed Nov 10 08:37:14 2004 From: Alan.Coopersmith at Sun.COM (Alan Coopersmith) Date: Wed Nov 10 13:26:54 2004 Subject: [Xprint] Re: [Fwd: cfb conversion effort (was Re: Debugging X.org drivers?)] In-Reply-To: <4191B87E.1050506@sun.com> References: <419194AC.7A5A6117@nrubsig.org> <4191B87E.1050506@sun.com> Message-ID: <419243BA.3020206@sun.com> Stuart Kreitman wrote: > we briefly toyed with porting m64 and vfb to use fb in Xsun. > It only took a few hours, and it came up, but we didn't pursue it- not > on our main path. Well, it only took a few hours to get m64 90% of the way converted. The last 10% of code would have been 90% of the work though, since what was left were the bits for dealing with the Xsun Multi-Plane Group functionality, which is supported in Xsun's cfb, but not in fb. -- -Alan Coopersmith- alan.coopersmith@sun.com Sun Microsystems, Inc. - X Window System Engineering From Stuart.Kreitman at Sun.COM Tue Nov 9 22:43:10 2004 From: Stuart.Kreitman at Sun.COM (Stuart Kreitman) Date: Wed Nov 10 23:04:26 2004 Subject: [Xprint] Re: [Fwd: cfb conversion effort (was Re: Debugging X.org drivers?)] In-Reply-To: <419194AC.7A5A6117@nrubsig.org> References: <419194AC.7A5A6117@nrubsig.org> Message-ID: <4191B87E.1050506@sun.com> we briefly toyed with porting m64 and vfb to use fb in Xsun. It only took a few hours, and it came up, but we didn't pursue it- not on our main path. skk Roland Mainz wrote: >Hi! > >---- > >I found the email which said that fb doesn't support some GC operation >overiding... >-- snip -- >Intermediate challenge would be something like sunleo or sunffb, where >magic >GC handling is used to implement primitive acceleration - [...] This is >pretty >gross and fb doesn't expose the same functionality; >-- snip -- >... I didn't checked that in detail but it sounds like there would be a >huge problem with converting the PCL drivers from cfb over to fb (or >not... I didn't investigate that in detail yet... right now I stil don't >dare to touch the PCL drivers in the hope that HP will contribute their >drivers back to Xorg (changing the Xorg drivers may make the merging of >the HP versions more difficult)) ... ;-( > >-------- Original Message -------- >Subject: cfb conversion effort (was Re: Debugging X.org drivers?) >Date: Sun, 31 Oct 2004 02:07:14 -0400 >From: Adam Jackson >To: xorg@freedesktop.org >CC: Roland Mainz ,Jim Gettys > >References: <41826D75.906.4AEE501E@localhost> ><200410301759.49970.ajax@nwnk.net> <418466A8.8AE9401F@nrubsig.org> > >On Sunday 31 October 2004 00:14, Roland Mainz wrote: > > >>Adam Jackson wrote: >> >> >>>Kendall, I'm for some reason thinking that the SciTech drivers were based >>>on the cfb framebuffer core. cfb will not work under dlloader with 6.8 >>>without a patch: >>> >>>http://freedesktop.org/bugzilla/show_bug.cgi?id=1114 >>> >>>but you may be better off switching to fb. >>> >>> >>Do you have any example patch which shows how to turn a driver from cfb >>over to fb ? HP's PCL drivers use cfb extensively and it may be nice to >>switch them over, too... >> >> > >Sure. One trivial example is the RealVNC conversion patch Kristian >H?gsberg >did: http://www.mail-archive.com/vnc-list@realvnc.com/msg14387.html > >For drivers that treat the fb layer as something of a black box, this is >all >you need to do. Most of the xfree86 ddx drivers are of this sort. >Until >fairly recently there was still optional cfb support in six of the >drivers, >and http://freedesktop.org/bugzilla/show_bug.cgi?id=1192 shows the >changes I >made to drop that support. In all but s3virge this support was disabled >at >compile time, and in s3virge the cfb code was slower and, as with cfb in >general, didn't support Render (and therefore Composite). > >Intermediate challenge would be something like sunleo or sunffb, where >magic >GC handling is used to implement primitive acceleration - double >entendre on >"primitive" totally intended. This is pretty gross and fb doesn't >expose the >same functionality; I suspect it can be dropped in most cases without >too >much pain. There's an experimental patch to convert sunleo to fb: >http://freedesktop.org/bugzilla/show_bug.cgi?id=1259 >which I have received no feedback on as of yet, and I don't have the >hardware >to verify it. sunffb is left as an exercise for the reader. > >The final step would be converting our overlay support to use fb. I >don't >even know where to begin here, largely for lack of hardware. I see a >couple >of functions in the fb layer that look like they're intended for overlay >support. I've been tempted to just drop our overlay support altogether >to >see who complains; my guess is, roughly, nobody. > >- ajax > > From jhein at timing.com Fri Nov 12 11:09:18 2004 From: jhein at timing.com (John E Hein) Date: Fri Nov 12 13:10:16 2004 Subject: [Xprint] printing PCL In-Reply-To: <16774.45355.730784.356124@gromit.timing.com> References: <16774.45355.730784.356124@gromit.timing.com> Message-ID: <16788.64590.771437.664392@gromit.timing.com> John E Hein wrote at 14:56 -0700 on Nov 1, 2004: > x.org 6.8.1 > I copied the HPLJ4050-PS model configuration to HPLJ4050-PCL5 and > changed instances of "POSTSCRIPT 2" to "PCL 5". > > When I start Xprt, I get: > > > No matching visual for __GLcontextMode with visual class = 1 (32774), nplanes = 8 > No matching visual for __GLcontextMode with visual class = 2 (32773), nplanes = 8 > No matching visual for __GLcontextMode with visual class = 4 (32770), nplanes = 8 > No matching visual for __GLcontextMode with visual class = 4 (32770), nplanes = 8 > No matching visual for __GLcontextMode with visual class = 4 (32770), nplanes = 8 > No matching visual for __GLcontextMode with visual class = 4 (32770), nplanes = 8 > No matching visual for __GLcontextMode with visual class = 5 (32771), nplanes = 8 > No matching visual for __GLcontextMode with visual class = 5 (32771), nplanes = 8 > No matching visual for __GLcontextMode with visual class = 5 (32771), nplanes = 8 > No matching visual for __GLcontextMode with visual class = 5 (32771), nplanes = 8 > No matching visual for __GLcontextMode with visual class = 0 (32775), nplanes = 8 I got rid of this message on startup by using ... *xp-ddx-identifier: XP-PCL-COLOR instead of ... *xp-ddx-identifier: XP-PCL-MONO in HPLJ4050-PCL5/model-config > When I try to print (xphelloworld), I get: > > xphelloworld: Error: no DPI set (or no default DPI provided by server) while trying to print. But I still get this even though I have this... HPLJ4050-PCL5.default-printer-resolution: 600 ... in /usr/X11R6/lib/X11/xserver/C/print/attributes/document > Is printing to PCL supposed to be working? Anyone? Am I doing something wrong? Printing to the PS version of this printer works fine. From mmata at multimatic.com Tue Nov 16 18:12:12 2004 From: mmata at multimatic.com (Marcelino Mata) Date: Tue Nov 16 18:13:03 2004 Subject: [Xprint] Monochrome printing instead of Greyscale or Color Message-ID: <8ECF2CA4D23BEE46A8D2D4DF19C0A87202403B@mtcmail2003.mtcdom.multimatic.com> This might be a simple question which is posted somewhere but searching FAQ and Google for several hours did not get any hits. While I am trying to get monochrome printing under Solaris 8 Sparc, I found I get the same behaviour under WinXP. I am printing from Firefox 1.0 under Solaris and WinXP. Is there a setting which forces monochrome printing instead of greyscale or color? For example, yellow text shows up as very faint grey. I am using the XPrint Server Glue pkg instead of the Xprint Server since I had issues with the non-native Solaris Xprt at one time. As I have the same problem under WinXP, I do not think the problem is Xprt related. Is this a Firefox issue not Xprint? Marcelino -------------- next part -------------- An HTML attachment was scrubbed... URL: http://mozdev.org/pipermail/xprint/attachments/20041116/c9513349/attachment.htm From ted at cypress.com Tue Nov 16 17:22:19 2004 From: ted at cypress.com (Thomas Dodd) Date: Tue Nov 16 18:23:48 2004 Subject: [Xprint] Monochrome printing instead of Greyscale or Color In-Reply-To: <8ECF2CA4D23BEE46A8D2D4DF19C0A87202403B@mtcmail2003.mtcdom.multimatic.com> References: <8ECF2CA4D23BEE46A8D2D4DF19C0A87202403B@mtcmail2003.mtcdom.multimatic.com> Message-ID: <419A8BAB.4000503@cypress.com> Marcelino Mata wrote: > Is there a setting which forces monochrome printing instead of greyscale > or color? For example, yellow text shows up as very faint grey. This is an app issue, not the print subsystem. And it's a difficult one to do anything with. How do you decice on black or white? Is Yellow black or white? What about red? What if the back ground is dark? If it's just text, your best bet is to save the html, and translate it to text(or use a text only browser without colored text). From david.c.mores at baesystems.com Wed Nov 17 16:52:32 2004 From: david.c.mores at baesystems.com (David C. Mores) Date: Tue Nov 23 11:00:09 2004 Subject: [Xprint] Xprint web page - missing stuff/broken links Message-ID: <419BC820.9060903@baesystems.com> The Xprint releases page talks about a build being available for HP-UX, but I cannot find it. Where is it? I tried to build Xprint from sources on HP-UX 11.11, but it failed. One of the Makefiles has an absolute hard coded path to the C compiler that fails. The Xprint bug page has two links at the top of the page for new bugs and listing open bugs. Both links fail - (bugs with bugs). Hey, looks like a few things could use some attention here. Please advise. Dave -- BAE SYSTEMS /* David C. Mores*/ *Principal Computer Resource Specialist 603-885-4641 david.c.mores@baesystems.com Post Office Box 868, PTP2-2C03 Nashua, NH 03061-0868* -------------- next part -------------- Skipped content of type multipart/related From dparsons at debian.org Wed Nov 24 11:25:44 2004 From: dparsons at debian.org (Drew Parsons) Date: Tue Nov 23 19:27:59 2004 Subject: [Xprint] problem running Xprint on amd64 (x86-64) In-Reply-To: <419BC820.9060903@baesystems.com> References: <419BC820.9060903@baesystems.com> Message-ID: <1101255944.7638.75.camel@pug.anu.edu.au> One of my Debian users has experienced some problems running Xprint on amd64 (x86-64). Originally he was getting a segfault (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=278510) He now reports the segfault is no longer occuring, after release of a newer Debian revision. Since it's still the same Xprint v9.001, I presume the change has been in libc6 or some other library for amd64 (not that libc6 has changed for amd64 over this time, but anyway. Maybe they use gcc-3.4 instead of gcc-3.3?). However, he reports that Xprint is nevertheless still not working, although it is no longer segfaulting: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282655&repeatmerged=no Xprt is running, but /etc/init.d/xprint thinks it has stopped. Since the original bug was specific to amd64, it occurs to me that the second might be as well. But the error is happening in /etc/init.d/xprint, not in Xprt. Support for amd64 is still "under development", it's not yet "fully supported" by Debian. So I'm not sure how much of his troubles are due to bugs in standard libraries (libc etc) for amd64, and how much could be Xprint's. The problem is not clear enough for me to file an Xprint bug. But I thought it might be useful to raise it on the mailing list for further thought. Debian amd64 porters - can any of you confirm that Xprint (package xprt-xprintorg) is working successfully for you? Test with xphelloworld or by printing from mozilla. Regards, Drew Parsons From dparsons at debian.org Wed Nov 24 20:17:55 2004 From: dparsons at debian.org (Drew Parsons) Date: Wed Nov 24 04:19:54 2004 Subject: [Xprint] Re: problem running Xprint on amd64 (x86-64) In-Reply-To: <1101255944.7638.75.camel@pug.anu.edu.au> References: <419BC820.9060903@baesystems.com> <1101255944.7638.75.camel@pug.anu.edu.au> Message-ID: <1101287875.7638.132.camel@pug.anu.edu.au> On Wed, 2004-11-24 at 11:25 +1100, Drew Parsons wrote: > One of my Debian users has experienced some problems running Xprint on > amd64 (x86-64). > > Originally he was getting a segfault > (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=278510) > > He now reports the segfault is no longer occuring, after release of a > newer Debian revision. The bug reporter has now clarified that the segfault is in fact happening after all. The running instance of Xprt that he thought he saw was from a chroot, not the instance he was trying to print through. I guess that makes the situation a bit more straightforward: there is a segfault in Xprt on amd64 which needs to be addressed. Drew From dparsons at debian.org Fri Nov 26 10:58:12 2004 From: dparsons at debian.org (Drew Parsons) Date: Thu Nov 25 19:00:17 2004 Subject: [Xprint] Is the locale being used sensibly by Xprint? LANG and LC_CTYPE are both used. In-Reply-To: <8ECF2CA4D23BEE46A8D2D4DF19C0A87202403B@mtcmail2003.mtcdom.multimatic.com> References: <8ECF2CA4D23BEE46A8D2D4DF19C0A87202403B@mtcmail2003.mtcdom.multimatic.com> Message-ID: <1101427092.21768.34.camel@pug.anu.edu.au> A Canadian user has reported trouble getting the correct paper to appear under mozilla. He needs to use letter, but mozilla displays a4 instead. His bug report is at http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=282806 I presume Xprint is working correctly as written, and that he is seeing this behaviour because he has LC_CTYPE set to "C", even though he has LANG=en_CA. xc/programs/Xserver/Xprint/attributes.c uses LANG in XpGetConfigDir( ), but uses LC_CTYPE in XpSpoolerGetServerAttributes, which I gather is the one reading in default-medium. Does this behaviour make sense? Should the same locale variable be used in both places? Would it make better sense to use LC_PAPER in both places? Is it worth filing a bug report about this question? ------ A related but separate question, Debian allows the system paper to be defined in /etc/papersize, and it would be nice for Xprint's default-medium to be set by it. Is /etc/papersize a common mechanism found in all or most unices and linuxes? Drew From jfl at robinlea.com Tue Nov 30 19:20:53 2004 From: jfl at robinlea.com (John Francis Lee) Date: Tue Nov 30 07:22:29 2004 Subject: [Xprint] xprint produces no output Message-ID: <1101817254.32054.10.camel@ws8.kic.muangchiangrai.net> Greetings, I have just installed FC3 and have configured my Ricoh AP1600 using the AP2000 printer driver, as suggested by personnel at Ricoh on their list. I have downloaded and installed xprint-2004-07-07- release_009_001-0.9.001.i386.rpm, started the daemon, then logged off and back on to initialize the XPSERVERLIST. [jfl@ws8 jfl-old]$ xplsprinters printer: ricoh@:33 printer: xp_ps_spooldir_tmp_Xprintjobs@:33 printer: xp_pdf_spooldir_tmp_Xprintjobs@:33 Now when I try to print a page from Firefox it takes an inordinately long time to process the page, and when it is finally processed, the lights on my ricoh flicker, the lcd says "processing"... and nothing comes out of the printer. It is once again "ready" to print. What can be going wrong here? I am trying to use xprint so that I can print Thai characters correctly from a browser. I have never been able to do so using the mozilla products, from Mozilla 1.0 through Firefox 1.0. I thought perhaps things had finally progressed to where this would be possible, noting redhat's advice to set MOZ_ENABLE_PANGO=1, but no joy yet. I remain the lone fool bozo in Thailand who insists on running software that cannot print Thai from the internet. Microsoft has been doing it for years of course. Any help would be appreciated. Thanks. -- John Francis Lee 1/9-10 Thanon Trairat Muang Chiang Rai 57000 Thailand From jstumpel at planet.nl Tue Nov 30 18:39:48 2004 From: jstumpel at planet.nl (Jan Willem Stumpel) Date: Tue Nov 30 12:44:16 2004 Subject: [Xprint] xprint produces no output In-Reply-To: <1101817254.32054.10.camel@ws8.kic.muangchiangrai.net> References: <1101817254.32054.10.camel@ws8.kic.muangchiangrai.net> Message-ID: <41ACB064.6040500@my.home> John Francis Lee wrote: > Now when I try to print a page from Firefox it takes an > inordinately long time to process the page, and when it is > finally processed, the lights on my ricoh flicker, the lcd says > "processing"... and nothing comes out of the printer. It is > once again "ready" to print. > > What can be going wrong here? Does *nothing* come out of the printer? Not even blank paper? If blank paper comes out, perhaps xprint is printing at the wrong scale. If the page you are printing is hugely blown up, you'd see margin space only. Have you tried printing to file and looking at the file with gv? Can you supply the URL of a good Thai "test page" to try it on? Regards, Jan From anders at netinsight.se Wed Nov 24 10:15:16 2004 From: anders at netinsight.se (Anders =?iso-8859-1?Q?Bostr=F6m?=) Date: Tue Dec 7 08:29:56 2004 Subject: [Xprint] Re: problem running Xprint on amd64 (x86-64) In-Reply-To: <1101255944.7638.75.camel@pug.anu.edu.au> References: <419BC820.9060903@baesystems.com> <1101255944.7638.75.camel@pug.anu.edu.au> Message-ID: <20041124.101516.113806010.anders@netinsight.se> >>>>> "DP" == Drew Parsons writes: DP> One of my Debian users has experienced some problems running Xprint on DP> amd64 (x86-64). This would be me... DP> Originally he was getting a segfault DP> (http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=278510) DP> He now reports the segfault is no longer occuring, after release of a DP> newer Debian revision. Since it's still the same Xprint v9.001, I DP> presume the change has been in libc6 or some other library for amd64 DP> (not that libc6 has changed for amd64 over this time, but anyway. Maybe DP> they use gcc-3.4 instead of gcc-3.3?). This was a misstake, the segfault is still occuring for me (and I just reopened bug# 278510 again). The problem is still that Xprt segfaults on start, see http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=278510 for a strace and bt. Has anyone Xprt up and running in 64-bit mode an amd64? / Anders