Menu
▾
▴
gimp-print-devel
You can subscribe to this list here.
| 2000 |
Jan
(111) |
Feb
(412) |
Mar
(133) |
Apr
(187) |
May
(377) |
Jun
(355) |
Jul
(129) |
Aug
(316) |
Sep
(412) |
Oct
(258) |
Nov
(260) |
Dec
(228) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2001 |
Jan
(291) |
Feb
(497) |
Mar
(341) |
Apr
(105) |
May
(127) |
Jun
(97) |
Jul
(348) |
Aug
(195) |
Sep
(353) |
Oct
(516) |
Nov
(454) |
Dec
(99) |
| 2002 |
Jan
(125) |
Feb
(232) |
Mar
(222) |
Apr
(160) |
May
(147) |
Jun
(97) |
Jul
(199) |
Aug
(275) |
Sep
(411) |
Oct
(355) |
Nov
(371) |
Dec
(326) |
| 2003 |
Jan
(314) |
Feb
(181) |
Mar
(166) |
Apr
(90) |
May
(192) |
Jun
(137) |
Jul
(91) |
Aug
(57) |
Sep
(59) |
Oct
(67) |
Nov
(202) |
Dec
(158) |
| 2004 |
Jan
(67) |
Feb
(81) |
Mar
(142) |
Apr
(124) |
May
(190) |
Jun
(245) |
Jul
(124) |
Aug
(199) |
Sep
(182) |
Oct
(92) |
Nov
(285) |
Dec
(173) |
| 2005 |
Jan
(111) |
Feb
(74) |
Mar
(90) |
Apr
(275) |
May
(133) |
Jun
(106) |
Jul
(215) |
Aug
(142) |
Sep
(131) |
Oct
(135) |
Nov
(75) |
Dec
(76) |
| 2006 |
Jan
(173) |
Feb
(96) |
Mar
(127) |
Apr
(226) |
May
(227) |
Jun
(83) |
Jul
(101) |
Aug
(122) |
Sep
(118) |
Oct
(27) |
Nov
(76) |
Dec
(58) |
| 2007 |
Jan
(204) |
Feb
(137) |
Mar
(115) |
Apr
(50) |
May
(135) |
Jun
(111) |
Jul
(57) |
Aug
(40) |
Sep
(36) |
Oct
(36) |
Nov
(77) |
Dec
(145) |
| 2008 |
Jan
(159) |
Feb
(52) |
Mar
(77) |
Apr
(59) |
May
(80) |
Jun
(105) |
Jul
(119) |
Aug
(225) |
Sep
(58) |
Oct
(173) |
Nov
(64) |
Dec
(94) |
| 2009 |
Jan
(61) |
Feb
(13) |
Mar
(70) |
Apr
(115) |
May
(48) |
Jun
(50) |
Jul
(34) |
Aug
(74) |
Sep
(30) |
Oct
(95) |
Nov
(132) |
Dec
(12) |
| 2010 |
Jan
(40) |
Feb
(22) |
Mar
(10) |
Apr
(5) |
May
(10) |
Jun
(73) |
Jul
(73) |
Aug
(74) |
Sep
(117) |
Oct
(33) |
Nov
(34) |
Dec
(41) |
| 2011 |
Jan
(42) |
Feb
(38) |
Mar
(60) |
Apr
(6) |
May
(26) |
Jun
(52) |
Jul
(16) |
Aug
(21) |
Sep
(49) |
Oct
(48) |
Nov
(64) |
Dec
(121) |
| 2012 |
Jan
(112) |
Feb
(81) |
Mar
(92) |
Apr
(37) |
May
(57) |
Jun
(142) |
Jul
(65) |
Aug
(43) |
Sep
(33) |
Oct
(81) |
Nov
(130) |
Dec
(63) |
| 2013 |
Jan
(63) |
Feb
(32) |
Mar
(80) |
Apr
(48) |
May
(44) |
Jun
(79) |
Jul
(86) |
Aug
(91) |
Sep
(43) |
Oct
(95) |
Nov
(130) |
Dec
(117) |
| 2014 |
Jan
(283) |
Feb
(206) |
Mar
(90) |
Apr
(57) |
May
(105) |
Jun
(66) |
Jul
(87) |
Aug
(30) |
Sep
(54) |
Oct
(125) |
Nov
(45) |
Dec
(36) |
| 2015 |
Jan
(58) |
Feb
(51) |
Mar
(59) |
Apr
(75) |
May
(70) |
Jun
(52) |
Jul
(58) |
Aug
(72) |
Sep
(184) |
Oct
(157) |
Nov
(91) |
Dec
(90) |
| 2016 |
Jan
(89) |
Feb
(61) |
Mar
(57) |
Apr
(86) |
May
(46) |
Jun
(63) |
Jul
(71) |
Aug
(60) |
Sep
(207) |
Oct
(139) |
Nov
(76) |
Dec
(68) |
| 2017 |
Jan
(112) |
Feb
(91) |
Mar
(138) |
Apr
(79) |
May
(36) |
Jun
(20) |
Jul
(105) |
Aug
(71) |
Sep
(51) |
Oct
(114) |
Nov
(148) |
Dec
(79) |
| 2018 |
Jan
(118) |
Feb
(107) |
Mar
(111) |
Apr
(127) |
May
(60) |
Jun
(63) |
Jul
(49) |
Aug
(18) |
Sep
(134) |
Oct
(68) |
Nov
(91) |
Dec
(27) |
| 2019 |
Jan
(41) |
Feb
(63) |
Mar
(37) |
Apr
(42) |
May
(44) |
Jun
(81) |
Jul
(53) |
Aug
(21) |
Sep
(62) |
Oct
(55) |
Nov
(41) |
Dec
(57) |
| 2020 |
Jan
(14) |
Feb
(29) |
Mar
(33) |
Apr
(20) |
May
(19) |
Jun
(9) |
Jul
(5) |
Aug
(23) |
Sep
(30) |
Oct
(29) |
Nov
(58) |
Dec
(139) |
| 2021 |
Jan
(62) |
Feb
(117) |
Mar
(13) |
Apr
(17) |
May
(23) |
Jun
(28) |
Jul
(7) |
Aug
(29) |
Sep
(56) |
Oct
(21) |
Nov
(36) |
Dec
(14) |
| 2022 |
Jan
(10) |
Feb
(28) |
Mar
(18) |
Apr
(19) |
May
(18) |
Jun
(3) |
Jul
(14) |
Aug
(11) |
Sep
(12) |
Oct
(4) |
Nov
|
Dec
(5) |
| 2023 |
Jan
|
Feb
|
Mar
(5) |
Apr
|
May
(2) |
Jun
(8) |
Jul
(2) |
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
| 2024 |
Jan
(5) |
Feb
|
Mar
|
Apr
|
May
(1) |
Jun
(1) |
Jul
(51) |
Aug
(31) |
Sep
(10) |
Oct
(14) |
Nov
(12) |
Dec
(14) |
| 2025 |
Jan
(17) |
Feb
(5) |
Mar
(30) |
Apr
(2) |
May
(4) |
Jun
(9) |
Jul
(5) |
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Ane M. B. <ane...@sh...> - 2019-02-12 18:54:33
|
I have an iBook G4 running Mac OS 10.5.8. I am trying to print to my Canon MG7700 series printer wirelessly over my local network, but nothing comes out. Is it possible to do this or is there a fix? Many thanks, Tom |
|
From: Gernot H. <aik...@gm...> - 2019-02-12 14:36:30
|
On Tue, Feb 12, 2019 at 11:03 PM Rob Pallard <rob...@gm...> wrote: Hello Rob, > I am trying to print to a Maxify MB2120 printer from Mac OS 10.6.8 Thank you for your report. Is that with gutenprint 5.2.14? > The printer//fax setup option recognizes the device and sees ink levels and can abort print jobs. When I try to print even a text file, I simply get reams of paper output. There is very faint, illegible printing on some pages. I think this printer is still experimental, but no-one has reported a problem so far. The same modes as on the iB4000 are used on the MB2100 series. So can I ask what your settings are, for media type, size, tray, resolution mode, colour mode? I suggest a test with the monochrome mode "600x600 DPI MONO" to see if that fairly simple mode works. A CUPS debug log would help also. Best regards, Gernot Hassenpflug |
|
From: Rob P. <rob...@gm...> - 2019-02-12 13:25:03
|
I am trying to print to a Maxify MB2120 printer from Mac OS 10.6.8 The printer//fax setup option recognizes the device and sees ink levels and can abort print jobs. When I try to print even a text file, I simply get reams of paper output. There is very faint, illegible printing on some pages. Any suggestions? thanks rob pallard |
|
From: Steve L. <sle...@ya...> - 2019-02-11 17:19:32
|
Rather, it is my pkg-config path. I am rebuilding now.
Steve Letter You're never to old to learn something stupid. -- unknown
On Monday, February 11, 2019, 12:02:32 PM EST, Steve Letter via Gimp-print-devel <gim...@li...> wrote:
I am missing something on my configure line it seems now.
Steve Letter
On Feb 11, 2019, at 10:59 AM, Steve Letter via Gimp-print-devel <gim...@li...> wrote:
I would guess something on my build system, most likely the usb library. 5.2.14-pre2 may have been built after an OS upgrade causing an issue we didn’t catch.
Steve Letter
On Feb 11, 2019, at 8:25 AM, Robert Krawitz <rl...@al...> wrote:
On Mon, 11 Feb 2019 07:17:26 -0500, Solomon Peachy wrote:
On Sun, Feb 10, 2019 at 08:25:01PM -0800, Matt Broughton wrote:
Steve, it looks like something changed in the build process between
v5.2.13 and 5.2.14-pre2. Beginning with 5.2.14-pre2 the
gutenprint52+usb backend was not included in the distribution. I
discovered it as I was testing the Gutenprint drivers after
transferring to a new MacBook Pro.
That explains the bug reports. :/
Indeed.
Matt or Steve, do you know which particular change set caused this to
happen?
--
Robert Krawitz <rl...@al...>
*** MIT Engineers A Proud Tradition http://mitathletics.com ***
Member of the League for Programming Freedom -- http://ProgFree.org
Project lead for Gutenprint -- http://gimp-print.sourceforge.net
"Linux doesn't dictate how I work, I dictate how Linux works."
--Eric Crampton
_______________________________________________
Gimp-print-devel mailing list
Gim...@li...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
_______________________________________________
Gimp-print-devel mailing list
Gim...@li...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
_______________________________________________
Gimp-print-devel mailing list
Gim...@li...
https://lists.sourceforge.net/lists/listinfo/gimp-print-devel
|
|
From: Steve L. <sle...@ya...> - 2019-02-11 17:01:57
|
I am missing something on my configure line it seems now. Steve Letter > On Feb 11, 2019, at 10:59 AM, Steve Letter via Gimp-print-devel <gim...@li...> wrote: > > I would guess something on my build system, most likely the usb library. 5.2.14-pre2 may have been built after an OS upgrade causing an issue we didn’t catch. > > Steve Letter > >> On Feb 11, 2019, at 8:25 AM, Robert Krawitz <rl...@al...> wrote: >> >>> On Mon, 11 Feb 2019 07:17:26 -0500, Solomon Peachy wrote: >>>> On Sun, Feb 10, 2019 at 08:25:01PM -0800, Matt Broughton wrote: >>>> Steve, it looks like something changed in the build process between >>>> v5.2.13 and 5.2.14-pre2. Beginning with 5.2.14-pre2 the >>>> gutenprint52+usb backend was not included in the distribution. I >>>> discovered it as I was testing the Gutenprint drivers after >>>> transferring to a new MacBook Pro. >>> >>> That explains the bug reports. :/ >> >> Indeed. >> >> Matt or Steve, do you know which particular change set caused this to >> happen? >> -- >> Robert Krawitz <rl...@al...> >> >> *** MIT Engineers A Proud Tradition http://mitathletics.com *** >> Member of the League for Programming Freedom -- http://ProgFree.org >> Project lead for Gutenprint -- http://gimp-print.sourceforge.net >> >> "Linux doesn't dictate how I work, I dictate how Linux works." >> --Eric Crampton >> >> >> _______________________________________________ >> Gimp-print-devel mailing list >> Gim...@li... >> https://lists.sourceforge.net/lists/listinfo/gimp-print-devel > _______________________________________________ > Gimp-print-devel mailing list > Gim...@li... > https://lists.sourceforge.net/lists/listinfo/gimp-print-devel |
|
From: Steve L. <sle...@ya...> - 2019-02-11 16:00:11
|
I would guess something on my build system, most likely the usb library. 5.2.14-pre2 may have been built after an OS upgrade causing an issue we didn’t catch. Steve Letter >> On Feb 11, 2019, at 8:25 AM, Robert Krawitz <rl...@al...> wrote: >> >>> On Mon, 11 Feb 2019 07:17:26 -0500, Solomon Peachy wrote: >>> On Sun, Feb 10, 2019 at 08:25:01PM -0800, Matt Broughton wrote: >>> Steve, it looks like something changed in the build process between >>> v5.2.13 and 5.2.14-pre2. Beginning with 5.2.14-pre2 the >>> gutenprint52+usb backend was not included in the distribution. I >>> discovered it as I was testing the Gutenprint drivers after >>> transferring to a new MacBook Pro. >> >> That explains the bug reports. :/ > > Indeed. > > Matt or Steve, do you know which particular change set caused this to > happen? > -- > Robert Krawitz <rl...@al...> > > *** MIT Engineers A Proud Tradition http://mitathletics.com *** > Member of the League for Programming Freedom -- http://ProgFree.org > Project lead for Gutenprint -- http://gimp-print.sourceforge.net > > "Linux doesn't dictate how I work, I dictate how Linux works." > --Eric Crampton > > > _______________________________________________ > Gimp-print-devel mailing list > Gim...@li... > https://lists.sourceforge.net/lists/listinfo/gimp-print-devel |
|
From: Robert K. <rl...@al...> - 2019-02-11 13:26:06
|
On Mon, 11 Feb 2019 07:17:26 -0500, Solomon Peachy wrote: > On Sun, Feb 10, 2019 at 08:25:01PM -0800, Matt Broughton wrote: >> Steve, it looks like something changed in the build process between >> v5.2.13 and 5.2.14-pre2. Beginning with 5.2.14-pre2 the >> gutenprint52+usb backend was not included in the distribution. I >> discovered it as I was testing the Gutenprint drivers after >> transferring to a new MacBook Pro. > > That explains the bug reports. :/ Indeed. Matt or Steve, do you know which particular change set caused this to happen? -- Robert Krawitz <rl...@al...> *** MIT Engineers A Proud Tradition http://mitathletics.com *** Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton |
|
From: Solomon P. <pi...@sh...> - 2019-02-11 12:17:40
|
On Sun, Feb 10, 2019 at 08:25:01PM -0800, Matt Broughton wrote: > Steve, it looks like something changed in the build process between > v5.2.13 and 5.2.14-pre2. Beginning with 5.2.14-pre2 the > gutenprint52+usb backend was not included in the distribution. I > discovered it as I was testing the Gutenprint drivers after > transferring to a new MacBook Pro. That explains the bug reports. :/ - Solomon -- Solomon Peachy pizza at shaftnet dot org Coconut Creek, FL ^^ (email/xmpp) ^^ Quidquid latine dictum sit, altum videtur. |
|
From: Solomon P. <pi...@sh...> - 2019-02-11 12:16:25
|
On Mon, Feb 11, 2019 at 07:10:49AM +0000, Stefan Höllwerth wrote: > thanks that did the trick! - the fuji ask-300 is now printing. > I'm using gutenprint v5.3.1. Excellent! > I still got one issue. The color seems not correct. In my opinion the > images are too much of yellow color. Did you apply some ICC color > profile for your ask-300? Yes, I'm using the one Fujifilm suppled with their Windows driver. It's not perfect but it's a big improvement over stock. (If you grabbed the selphy_print repo, there's a copy under icm/Fujifilm) One of these days I'll get a proper spectrophotometer to generate my own profiles... - Solomon -- Solomon Peachy pizza at shaftnet dot org Coconut Creek, FL ^^ (email/xmpp) ^^ Quidquid latine dictum sit, altum videtur. |
|
From: Stefan H. <ste...@k-...> - 2019-02-11 07:11:05
|
Hello Solomon, thanks that did the trick! - the fuji ask-300 is now printing. I'm using gutenprint v5.3.1. I still got one issue. The color seems not correct. In my opinion the images are too much of yellow color. Did you apply some ICC color profile for your ask-300? thanks for you help Stefan -----Ursprüngliche Nachricht----- Von: Solomon Peachy <pi...@sh...> Gesendet: Freitag, 8. Februar 2019 15:22 An: Stefan Höllwerth <ste...@k-...> Cc: gim...@li... Betreff: Re: [Gimp-print-devel] Gurenprint Fuji-ASK300 On Fri, Feb 08, 2019 at 07:04:51AM +0000, Stefan Höllwerth wrote: > I tried to install the Fuji ask-300 printer with gutenprint 5.3 and > cups 2.2.1 on a raspberry pi The printer is listed as > "gutenprint53+usb://fujifilm-ask-300/159312". If I do print the cups > interface always shows "Invalid backend (fujifilm-ask-300)" Do you > have an idea what that could be? You'll need the image processing library and the various data files too: http://www.peachyphotos.com/blog/posts/201610061508-mitsubishi-cp-d70-family-working/ Beyond that, what version of Gutenprint are you using? Best results with the ASK300 will require compiling current code out of the gutenprint git repo. (BTW, I have an ASK-300, it works quite well..) - Solomon -- Solomon Peachy pizza at shaftnet dot org Coconut Creek, FL ^^ (email/xmpp) ^^ Quidquid latine dictum sit, altum videtur. |
|
From: Matt B. <wal...@ma...> - 2019-02-11 04:25:20
|
> On Feb 10, 2019, at 5:25 PM, Steve Letter via Gimp-print-devel <gim...@li...> wrote: > > I have been wondering if I have been missing some of the conversations, not having built a version for some time. I have seen a lot of changes and want to do a test build. > > This is the first I have seen about a build, is there a tar file for me? Steve, it looks like something changed in the build process between v5.2.13 and 5.2.14-pre2. Beginning with 5.2.14-pre2 the gutenprint52+usb backend was not included in the distribution. I discovered it as I was testing the Gutenprint drivers after transferring to a new MacBook Pro. Matt -- Matt Broughton wal...@ma... |
|
From: Robert K. <rl...@al...> - 2019-02-11 03:23:38
|
On Sun, 10 Feb 2019 20:25:30 -0500, Steve Letter wrote: > > --Apple-Mail-1422DA56-5A1C-4C37-B979-6477D5509D62 > Content-Type: text/plain; > charset=us-ascii > Content-Transfer-Encoding: quoted-printable > > I have been wondering if I have been missing some of the conversations, not having built a version for some time. I have seen a lot of changes and want to do a test build. > > This is the first I have seen about a build, is there a tar file for me? I'm building tarballs for 5.2.15-pre1 and 5.3.2-pre1. I should have those for you tomorrow. -- Robert Krawitz <rl...@al...> *** MIT Engineers A Proud Tradition http://mitathletics.com *** Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton |
|
From: Gernot H. <aik...@gm...> - 2019-02-11 03:00:22
|
On Mon, Feb 11, 2019 at 2:53 AM Elvira Mbodji <elv...@we...> wrote: > Hello, > > after installing your driver gutenprint-5.2.11 (for my Mac OS 10.11, El > Capitain) > Hello Elvira, Thank you for your report. There are a couple of things here that need further investigation from your side though. First, 5.2.11 is very old, you should be using the latest 5.2.14. This does likely not affect the printer functionality, as the MP540 has been supported for a long long time without problems, but it certainly impacts debugging. for the printer canon Pixma MP540 I was not able to print but got the error > message enclosed. > The error message is not very helpful, unfortunately. You would need to set logging to debug, and then attach the relevant CUPS error log for the printjob in question, to see which filter is causing a problem. If that filter is one of the CUPS or Ghostscript filters before the job reaches gutenprint, that would be a different bug to file with the relevant organization. However I have been able to scan using the scan button. > Scanning has nothing to do with gutenprint. And I am wondering now if you are really using the gutenprint driver for your printe, or if you are using a driver released by Canon in actual fact? Can you help me to also get a printing job done with my printer? > Probably yes, since the printer is well-supported. It is probably merely a matter of getting the relevant error information. Best regards, Gernot Hassenpflug |
|
From: Steve L. <sle...@ya...> - 2019-02-11 01:25:47
|
I have been wondering if I have been missing some of the conversations, not having built a version for some time. I have seen a lot of changes and want to do a test build. This is the first I have seen about a build, is there a tar file for me? Steve Letter > On Feb 10, 2019, at 10:37 AM, Robert Krawitz <rl...@al...> wrote: > > On Sat, 9 Feb 2019 20:05:15 -0800, Matt Broughton wrote: >>> I think a new release would be preferable. It's a lot easier to ask >>> "what version of Gutenprint are you using" (that's easily available) >>> than "have you installed the supplement" (d'uh, what's that, of course >>> I have!). >>> >>> We do have some changes from 5.2.14 IIRC. And then there's 5.3... >> >> A stopgap measure might be to have those who need the >> gutenprint52+usb backend revert back to v5.2.13. I checked and >> found the backend in that package. The missing backend appears to >> have started with v5.2.14-pre2. > > There are some important improvements in 5.2.14 (fixing a crash, and > the color problem that regressed in 5.2.13) that I'd really like to > get out as soon as practicable. > -- > Robert Krawitz <rl...@al...> > > *** MIT Engineers A Proud Tradition http://mitathletics.com *** > Member of the League for Programming Freedom -- http://ProgFree.org > Project lead for Gutenprint -- http://gimp-print.sourceforge.net > > "Linux doesn't dictate how I work, I dictate how Linux works." > --Eric Crampton |
|
From: Matt B. <wal...@ma...> - 2019-02-10 19:10:06
|
> On Feb 9, 2019, at 8:28 PM, Matt Broughton <wal...@ma...> wrote: > > > >> On Feb 9, 2019, at 5:58 PM, Robert Krawitz <rl...@al...> wrote: >> >> On Sat, 9 Feb 2019 17:38:15 -0800, Matt Broughton wrote: >>> I am pulling this snippet from the macos gutenprint52+usb backend thread. I think the discussion on the uninstaller would get buried otherwise. >>> >>>>> I will try to make a post about why there is so much troubler with out uninstaller. I got reminded of some of the nasties Apple tends to do with installs and using the Migration Assistant. Moving to a new laptop reminded me of the issues. My old laptop got some water on the keyboard and sparks started flying. I am glad that I keep two backups. >>>> >>>> I'd like to better understand the uninstaller situation. That does >>>> seem to cause problems. >>> >>> I'll describe the current situation. Problems from OS X 10.7 and before are similar but have some other specific issues. >> >> Thanks for this solution. >> >>> Every time you install software on macos by using an installer, as opposed to drag and drop, a receipt for what was installed and where it was installed is recorded in an invisible directory. I am sure Linux and Windows do similar things. The uninstaller has always relied on using this receipt to find out what Gutenprint installed and where. The list of files are then removed and the receipt removed. This has been the practice since Mac OX 10.3.x. >> >> Linux, "it's complicated". Different distributions have different >> package managers (Debian and its derivatives such as Ubuntu use dpkg >> and .deb files; Red Hat, SUSE, and their derivatives use RPM (although >> the RPMs, while of the same format, are not entirely mutually >> compatible), and on just about any distribution you can install things >> from source without any package management at all beyond >> configure/cmake,make,make install. >> >>> Currently, doing a system upgrade such as macos 10.12.x to macos 10.14.x leaves this receipt and the software files intact and no problem is encountered. The Gutenprint drivers work fine and the receipt is left in place. If the user uses Migration Assistant however, all bets are off. Migration will remove the software receipts for *all* third party software. Now when you try to run the uninstaller, it doesn't find any receipt and reports that there is nothing to remove. This is why we recommend reinstalling the software and then run the uninstaller again. This is contrary to common sense but is probably the easiest and safest way to proceed. We could always tell those that need to remove the software to delete a subdirectory in the /Library directory. In my mind, files in the /Library is a bit close to telling someone to remove system software. >> >> Can we inspect what's in /Library (or wherever) and determine that >> it's ours and delete it? Or do a pseudo-install ourselves as part of >> the uninstall? That feels like a real shot in the dark, but... > > The simplest solution is to just remove the /Library/Printers/Gutenprint.printerDriver directory. That would leave only some symlinks. That is where everything is located. There are symlinks that point to the executables, but those would be relatively harmless to leave in place. > >> But this sounds like a rather serious problem with Migration >> Assistant; what do other third party packages do? > > My guess is that vendors like Epson, Microsoft, and the like aren't that concerned or are unaware of the situation. Still others don't provide any sort of uninstaller. > >>> I can't think of an easy alternative to using the software receipt to find what needs to be removed. The uninstaller is meant to work for all installations of Gimp-Print and Gutenprint going back to Mac OS X 10.3. That pretty much precludes just including a file with the distribution that contains the files to be removed. There have been and probably will be changes in file names and locations that might cause problems using this method. If there are any other methods that seem reasonable, we should explore them. >> >> How far back do we need the uninstaller to work? Can we release a new >> version of the uninstaller that handles this situation, but only from >> 10.6 (oldest currently supported version of Gutenprint)? > > > I will have to check back to see when Apple made the change in dealing with receipts and how far back we need or should go. More importantly woulds be the point that we started using only the one directory in /Library/Printers for our software. We had been using the /usr structure before that. Apple suddenly blacklisted that directory and we changed. There is a long story why we never used the /usr/local/usr structure. > >>> It is probably worth noting that the current installer for Gutenprint does an uninstall of the old software prior to installation of the new software. If that part of the install fails, it does so quietly, with the assumption that whatever is currently being installed will overwrite the old files. >> >> Within 5.2, that's mostly true. The exceptions are probably largely >> harmless, other than being a small resource leak; pretty much all that >> matters comes from the root of printers.xml. Going from 5.2 to 5.3, >> that won't be true; the files go in a different root directory (5.3 >> vs. 5.2), although even there it all starts from known root files and >> what they refer to. Ads it turns out, the installer has a very robust uninstaller script that I believe covers all cases. I copied that and upped the authority to root by using sudo for all the cases where `/bin/rm -rf ` are found. If you want full testing on it, I won't be able to get to it until the end of the month. I should have some time then and access to my older computers where I can test it on Mac OS X 10.3.x through 10.6.x as desired. An alternative is to just change the new script to have an extension of .command and it becomes a double click format. Is there a way to have someone change a script to get an actual binary that could be signed? Apple's security is getting tighter and tighter. It is getting more and more cumbersome to use non-signed applications. Matt -- Matt Broughton wal...@ma... |
|
From: Elvira M. <elv...@we...> - 2019-02-10 17:28:31
|
Hello, after installing your driver gutenprint-5.2.11 (for my Mac OS 10.11, El Capitain) for the printer canon Pixma MP540 I was not able to print but got the error message enclosed. However I have been able to scan using the scan button. Can you help me to also get a printing job done with my printer? Many thanks Elvira Mbodji Grafikdesign & Illustration Elvira Mbodji Schilfstr. 16 82223 Eichenau Germany Tel. +49 8141/72555 elv...@we... <mailto:elv...@we...> |
|
From: Robert K. <rl...@al...> - 2019-02-10 15:37:38
|
On Sat, 9 Feb 2019 20:05:15 -0800, Matt Broughton wrote: >> I think a new release would be preferable. It's a lot easier to ask >> "what version of Gutenprint are you using" (that's easily available) >> than "have you installed the supplement" (d'uh, what's that, of course >> I have!). >> >> We do have some changes from 5.2.14 IIRC. And then there's 5.3... > > A stopgap measure might be to have those who need the > gutenprint52+usb backend revert back to v5.2.13. I checked and > found the backend in that package. The missing backend appears to > have started with v5.2.14-pre2. There are some important improvements in 5.2.14 (fixing a crash, and the color problem that regressed in 5.2.13) that I'd really like to get out as soon as practicable. -- Robert Krawitz <rl...@al...> *** MIT Engineers A Proud Tradition http://mitathletics.com *** Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton |
|
From: Matt B. <wal...@ma...> - 2019-02-10 04:28:52
|
> On Feb 9, 2019, at 5:58 PM, Robert Krawitz <rl...@al...> wrote: > > On Sat, 9 Feb 2019 17:38:15 -0800, Matt Broughton wrote: >> I am pulling this snippet from the macos gutenprint52+usb backend thread. I think the discussion on the uninstaller would get buried otherwise. >> >>>> I will try to make a post about why there is so much troubler with out uninstaller. I got reminded of some of the nasties Apple tends to do with installs and using the Migration Assistant. Moving to a new laptop reminded me of the issues. My old laptop got some water on the keyboard and sparks started flying. I am glad that I keep two backups. >>> >>> I'd like to better understand the uninstaller situation. That does >>> seem to cause problems. >> >> I'll describe the current situation. Problems from OS X 10.7 and before are similar but have some other specific issues. > > Thanks for this solution. > >> Every time you install software on macos by using an installer, as opposed to drag and drop, a receipt for what was installed and where it was installed is recorded in an invisible directory. I am sure Linux and Windows do similar things. The uninstaller has always relied on using this receipt to find out what Gutenprint installed and where. The list of files are then removed and the receipt removed. This has been the practice since Mac OX 10.3.x. > > Linux, "it's complicated". Different distributions have different > package managers (Debian and its derivatives such as Ubuntu use dpkg > and .deb files; Red Hat, SUSE, and their derivatives use RPM (although > the RPMs, while of the same format, are not entirely mutually > compatible), and on just about any distribution you can install things > from source without any package management at all beyond > configure/cmake,make,make install. > >> Currently, doing a system upgrade such as macos 10.12.x to macos 10.14.x leaves this receipt and the software files intact and no problem is encountered. The Gutenprint drivers work fine and the receipt is left in place. If the user uses Migration Assistant however, all bets are off. Migration will remove the software receipts for *all* third party software. Now when you try to run the uninstaller, it doesn't find any receipt and reports that there is nothing to remove. This is why we recommend reinstalling the software and then run the uninstaller again. This is contrary to common sense but is probably the easiest and safest way to proceed. We could always tell those that need to remove the software to delete a subdirectory in the /Library directory. In my mind, files in the /Library is a bit close to telling someone to remove system software. > > Can we inspect what's in /Library (or wherever) and determine that > it's ours and delete it? Or do a pseudo-install ourselves as part of > the uninstall? That feels like a real shot in the dark, but... The simplest solution is to just remove the /Library/Printers/Gutenprint.printerDriver directory. That would leave only some symlinks. That is where everything is located. There are symlinks that point to the executables, but those would be relatively harmless to leave in place. > But this sounds like a rather serious problem with Migration > Assistant; what do other third party packages do? My guess is that vendors like Epson, Microsoft, and the like aren't that concerned or are unaware of the situation. Still others don't provide any sort of uninstaller. >> I can't think of an easy alternative to using the software receipt to find what needs to be removed. The uninstaller is meant to work for all installations of Gimp-Print and Gutenprint going back to Mac OS X 10.3. That pretty much precludes just including a file with the distribution that contains the files to be removed. There have been and probably will be changes in file names and locations that might cause problems using this method. If there are any other methods that seem reasonable, we should explore them. > > How far back do we need the uninstaller to work? Can we release a new > version of the uninstaller that handles this situation, but only from > 10.6 (oldest currently supported version of Gutenprint)? I will have to check back to see when Apple made the change in dealing with receipts and how far back we need or should go. More importantly woulds be the point that we started using only the one directory in /Library/Printers for our software. We had been using the /usr structure before that. Apple suddenly blacklisted that directory and we changed. There is a long story why we never used the /usr/local/usr structure. >> It is probably worth noting that the current installer for Gutenprint does an uninstall of the old software prior to installation of the new software. If that part of the install fails, it does so quietly, with the assumption that whatever is currently being installed will overwrite the old files. > > Within 5.2, that's mostly true. The exceptions are probably largely > harmless, other than being a small resource leak; pretty much all that > matters comes from the root of printers.xml. Going from 5.2 to 5.3, > that won't be true; the files go in a different root directory (5.3 > vs. 5.2), although even there it all starts from known root files and > what they refer to. > -- > Robert Krawitz <rl...@al...> > -- Matt Broughton wal...@ma... |
|
From: Matt B. <wal...@ma...> - 2019-02-10 04:05:27
|
> On Feb 9, 2019, at 2:22 PM, Robert Krawitz <rl...@al...> wrote: > > On Sat, 9 Feb 2019 14:05:03 -0800, Matt Broughton wrote: >>> On Feb 9, 2019, at 1:38 PM, Robert Krawitz <rl...@al...> wrote: >>> >>> On Sat, 9 Feb 2019 09:59:05 -0800, Matt Broughton wrote: >>>> I was testing the Gutenprint v5.2.14 against macos 10.14.2. I found that both a USB Epson WorkForce 1100 and a networked Xerox Phaser 6180 color laser printer were fine. I did and do have a paper feed problem with my Epson printer that is posted in another thread, but that doesn't impact the fact that Gutenprint drivers work fine in macos 10.14.2. >>>> >>>> I don't have any Canon printers to test, but there seems to be enough questions about the working of Canon printers I thought I would take a look to make sure that the gutenprint52+usb backend was included in the macos release. The answer was a surprising no., It is not included. There is a symlink -- >>>> /usr/libexec/cups/backend/gutenprint52+usb -> /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/gutenprint52+usb >>>> The actual executable, however, was never installed. >>>> if test -f /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/gutenprint52+usb ; then echo good file ; else echo no file here; fi >>>> This returns "no file here" >>>> >>>> The scripts in the macosx directory in git shows that LIBUSB should be built and therefore picked up when ./configure is run. Might it be that LIBUSB never made it into the $PATH? >>>> >>>> Not having that backend would certainly cause problems problems for some users. >>> >>> So do we need to do a new release (5.2.15) for this? >>> >>> Also, can we get a build for 5.3? I'd like to do another 5.3 release >>> and would really like a Mac release for it. >>> -- >>> Robert Krawitz <rl...@al... <mailto:rl...@al...> <mailto:rl...@al... <mailto:rl...@al...>>> >> >> In my opinion, a release of 5.2.15 would be ideal. Certainly it would help those who are providing help with the Canon printers for macos. It is always difficult to get the exact model and operating system included in the original post about a problem. It usually takes two or three exchanges. Once all that information is obtained, then it would have to be checked against the list of printers that need the gutenprint52+usb backend. If they do need that backend, how do we provide it to them? I suppose we could have a "supplement or update" to what is there, but I think that would be the same amount of work as making a full release. > > I think a new release would be preferable. It's a lot easier to ask > "what version of Gutenprint are you using" (that's easily available) > than "have you installed the supplement" (d'uh, what's that, of course > I have!). > > We do have some changes from 5.2.14 IIRC. And then there's 5.3... A stopgap measure might be to have those who need the gutenprint52+usb backend revert back to v5.2.13. I checked and found the backend in that package. The missing backend appears to have started with v5.2.14-pre2. Matt -- Matt Broughton wal...@ma... |
|
From: Robert K. <rl...@al...> - 2019-02-10 02:02:59
|
On Sat, 9 Feb 2019 20:58:45 -0500 (EST), Robert Krawitz wrote: > On Sat, 9 Feb 2019 17:38:15 -0800, Matt Broughton wrote: >> I am pulling this snippet from the macos gutenprint52+usb backend thread. I think the discussion on the uninstaller would get buried otherwise. >> >>>> I will try to make a post about why there is so much troubler with out uninstaller. I got reminded of some of the nasties Apple tends to do with installs and using the Migration Assistant. Moving to a new laptop reminded me of the issues. My old laptop got some water on the keyboard and sparks started flying. I am glad that I keep two backups. >>> >>> I'd like to better understand the uninstaller situation. That does >>> seem to cause problems. >> >> I'll describe the current situation. Problems from OS X 10.7 and before are similar but have some other specific issues. > > Thanks for this solution. s/solution/explanation/ :-) -- Robert Krawitz <rl...@al...> *** MIT Engineers A Proud Tradition http://mitathletics.com *** Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton |
|
From: Robert K. <rl...@al...> - 2019-02-10 01:58:56
|
On Sat, 9 Feb 2019 17:38:15 -0800, Matt Broughton wrote: > I am pulling this snippet from the macos gutenprint52+usb backend thread. I think the discussion on the uninstaller would get buried otherwise. > >>> I will try to make a post about why there is so much troubler with out uninstaller. I got reminded of some of the nasties Apple tends to do with installs and using the Migration Assistant. Moving to a new laptop reminded me of the issues. My old laptop got some water on the keyboard and sparks started flying. I am glad that I keep two backups. >> >> I'd like to better understand the uninstaller situation. That does >> seem to cause problems. > > I'll describe the current situation. Problems from OS X 10.7 and before are similar but have some other specific issues. Thanks for this solution. > Every time you install software on macos by using an installer, as opposed to drag and drop, a receipt for what was installed and where it was installed is recorded in an invisible directory. I am sure Linux and Windows do similar things. The uninstaller has always relied on using this receipt to find out what Gutenprint installed and where. The list of files are then removed and the receipt removed. This has been the practice since Mac OX 10.3.x. Linux, "it's complicated". Different distributions have different package managers (Debian and its derivatives such as Ubuntu use dpkg and .deb files; Red Hat, SUSE, and their derivatives use RPM (although the RPMs, while of the same format, are not entirely mutually compatible), and on just about any distribution you can install things from source without any package management at all beyond configure/cmake,make,make install. > Currently, doing a system upgrade such as macos 10.12.x to macos 10.14.x leaves this receipt and the software files intact and no problem is encountered. The Gutenprint drivers work fine and the receipt is left in place. If the user uses Migration Assistant however, all bets are off. Migration will remove the software receipts for *all* third party software. Now when you try to run the uninstaller, it doesn't find any receipt and reports that there is nothing to remove. This is why we recommend reinstalling the software and then run the uninstaller again. This is contrary to common sense but is probably the easiest and safest way to proceed. We could always tell those that need to remove the software to delete a subdirectory in the /Library directory. In my mind, files in the /Library is a bit close to telling someone to remove system software. Can we inspect what's in /Library (or wherever) and determine that it's ours and delete it? Or do a pseudo-install ourselves as part of the uninstall? That feels like a real shot in the dark, but... But this sounds like a rather serious problem with Migration Assistant; what do other third party packages do? > I can't think of an easy alternative to using the software receipt to find what needs to be removed. The uninstaller is meant to work for all installations of Gimp-Print and Gutenprint going back to Mac OS X 10.3. That pretty much precludes just including a file with the distribution that contains the files to be removed. There have been and probably will be changes in file names and locations that might cause problems using this method. If there are any other methods that seem reasonable, we should explore them. How far back do we need the uninstaller to work? Can we release a new version of the uninstaller that handles this situation, but only from 10.6 (oldest currently supported version of Gutenprint)? > It is probably worth noting that the current installer for Gutenprint does an uninstall of the old software prior to installation of the new software. If that part of the install fails, it does so quietly, with the assumption that whatever is currently being installed will overwrite the old files. Within 5.2, that's mostly true. The exceptions are probably largely harmless, other than being a small resource leak; pretty much all that matters comes from the root of printers.xml. Going from 5.2 to 5.3, that won't be true; the files go in a different root directory (5.3 vs. 5.2), although even there it all starts from known root files and what they refer to. -- Robert Krawitz <rl...@al...> *** MIT Engineers A Proud Tradition http://mitathletics.com *** Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton |
|
From: Matt B. <wal...@ma...> - 2019-02-10 01:38:24
|
I am pulling this snippet from the macos gutenprint52+usb backend thread. I think the discussion on the uninstaller would get buried otherwise. >> I will try to make a post about why there is so much troubler with out uninstaller. I got reminded of some of the nasties Apple tends to do with installs and using the Migration Assistant. Moving to a new laptop reminded me of the issues. My old laptop got some water on the keyboard and sparks started flying. I am glad that I keep two backups. > > I'd like to better understand the uninstaller situation. That does > seem to cause problems. I'll describe the current situation. Problems from OS X 10.7 and before are similar but have some other specific issues. Every time you install software on macos by using an installer, as opposed to drag and drop, a receipt for what was installed and where it was installed is recorded in an invisible directory. I am sure Linux and Windows do similar things. The uninstaller has always relied on using this receipt to find out what Gutenprint installed and where. The list of files are then removed and the receipt removed. This has been the practice since Mac OX 10.3.x. Currently, doing a system upgrade such as macos 10.12.x to macos 10.14.x leaves this receipt and the software files intact and no problem is encountered. The Gutenprint drivers work fine and the receipt is left in place. If the user uses Migration Assistant however, all bets are off. Migration will remove the software receipts for *all* third party software. Now when you try to run the uninstaller, it doesn't find any receipt and reports that there is nothing to remove. This is why we recommend reinstalling the software and then run the uninstaller again. This is contrary to common sense but is probably the easiest and safest way to proceed. We could always tell those that need to remove the software to delete a subdirectory in the /Library directory. In my mind, files in the /Library is a bit close to telling someone to remove system software. I can't think of an easy alternative to using the software receipt to find what needs to be removed. The uninstaller is meant to work for all installations of Gimp-Print and Gutenprint going back to Mac OS X 10.3. That pretty much precludes just including a file with the distribution that contains the files to be removed. There have been and probably will be changes in file names and locations that might cause problems using this method. If there are any other methods that seem reasonable, we should explore them. It is probably worth noting that the current installer for Gutenprint does an uninstall of the old software prior to installation of the new software. If that part of the install fails, it does so quietly, with the assumption that whatever is currently being installed will overwrite the old files. -- Matt wal...@ma... |
|
From: Robert K. <rl...@al...> - 2019-02-09 22:22:49
|
On Sat, 9 Feb 2019 14:05:03 -0800, Matt Broughton wrote: >> On Feb 9, 2019, at 1:38 PM, Robert Krawitz <rl...@al...> wrote: >> >> On Sat, 9 Feb 2019 09:59:05 -0800, Matt Broughton wrote: >>> I was testing the Gutenprint v5.2.14 against macos 10.14.2. I found that both a USB Epson WorkForce 1100 and a networked Xerox Phaser 6180 color laser printer were fine. I did and do have a paper feed problem with my Epson printer that is posted in another thread, but that doesn't impact the fact that Gutenprint drivers work fine in macos 10.14.2. >>> >>> I don't have any Canon printers to test, but there seems to be enough questions about the working of Canon printers I thought I would take a look to make sure that the gutenprint52+usb backend was included in the macos release. The answer was a surprising no., It is not included. There is a symlink -- >>> /usr/libexec/cups/backend/gutenprint52+usb -> /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/gutenprint52+usb >>> The actual executable, however, was never installed. >>> if test -f /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/gutenprint52+usb ; then echo good file ; else echo no file here; fi >>> This returns "no file here" >>> >>> The scripts in the macosx directory in git shows that LIBUSB should be built and therefore picked up when ./configure is run. Might it be that LIBUSB never made it into the $PATH? >>> >>> Not having that backend would certainly cause problems problems for some users. >> >> So do we need to do a new release (5.2.15) for this? >> >> Also, can we get a build for 5.3? I'd like to do another 5.3 release >> and would really like a Mac release for it. >> -- >> Robert Krawitz <rl...@al... <mailto:rl...@al...>> > > In my opinion, a release of 5.2.15 would be ideal. Certainly it would help those who are providing help with the Canon printers for macos. It is always difficult to get the exact model and operating system included in the original post about a problem. It usually takes two or three exchanges. Once all that information is obtained, then it would have to be checked against the list of printers that need the gutenprint52+usb backend. If they do need that backend, how do we provide it to them? I suppose we could have a "supplement or update" to what is there, but I think that would be the same amount of work as making a full release. I think a new release would be preferable. It's a lot easier to ask "what version of Gutenprint are you using" (that's easily available) than "have you installed the supplement" (d'uh, what's that, of course I have!). We do have some changes from 5.2.14 IIRC. And then there's 5.3... > I'll let you and Steve determine what gets built and when. I will try to make a post about why there is so much troubler with out uninstaller. I got reminded of some of the nasties Apple tends to do with installs and using the Migration Assistant. Moving to a new laptop reminded me of the issues. My old laptop got some water on the keyboard and sparks started flying. I am glad that I keep two backups. I'd like to better understand the uninstaller situation. That does seem to cause problems. Apologies to all; this winter has been busy and I've had very little time to pay attention to Gutenprint. -- Robert Krawitz <rl...@al...> *** MIT Engineers A Proud Tradition http://mitathletics.com *** Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton |
|
From: Matt B. <wal...@ma...> - 2019-02-09 22:05:13
|
> On Feb 9, 2019, at 1:38 PM, Robert Krawitz <rl...@al...> wrote: > > On Sat, 9 Feb 2019 09:59:05 -0800, Matt Broughton wrote: >> I was testing the Gutenprint v5.2.14 against macos 10.14.2. I found that both a USB Epson WorkForce 1100 and a networked Xerox Phaser 6180 color laser printer were fine. I did and do have a paper feed problem with my Epson printer that is posted in another thread, but that doesn't impact the fact that Gutenprint drivers work fine in macos 10.14.2. >> >> I don't have any Canon printers to test, but there seems to be enough questions about the working of Canon printers I thought I would take a look to make sure that the gutenprint52+usb backend was included in the macos release. The answer was a surprising no., It is not included. There is a symlink -- >> /usr/libexec/cups/backend/gutenprint52+usb -> /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/gutenprint52+usb >> The actual executable, however, was never installed. >> if test -f /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/gutenprint52+usb ; then echo good file ; else echo no file here; fi >> This returns "no file here" >> >> The scripts in the macosx directory in git shows that LIBUSB should be built and therefore picked up when ./configure is run. Might it be that LIBUSB never made it into the $PATH? >> >> Not having that backend would certainly cause problems problems for some users. > > So do we need to do a new release (5.2.15) for this? > > Also, can we get a build for 5.3? I'd like to do another 5.3 release > and would really like a Mac release for it. > -- > Robert Krawitz <rl...@al... <mailto:rl...@al...>> In my opinion, a release of 5.2.15 would be ideal. Certainly it would help those who are providing help with the Canon printers for macos. It is always difficult to get the exact model and operating system included in the original post about a problem. It usually takes two or three exchanges. Once all that information is obtained, then it would have to be checked against the list of printers that need the gutenprint52+usb backend. If they do need that backend, how do we provide it to them? I suppose we could have a "supplement or update" to what is there, but I think that would be the same amount of work as making a full release. I'll let you and Steve determine what gets built and when. I will try to make a post about why there is so much troubler with out uninstaller. I got reminded of some of the nasties Apple tends to do with installs and using the Migration Assistant. Moving to a new laptop reminded me of the issues. My old laptop got some water on the keyboard and sparks started flying. I am glad that I keep two backups. Matt -- Matt wal...@ma... |
|
From: Robert K. <rl...@al...> - 2019-02-09 21:38:35
|
On Sat, 9 Feb 2019 09:59:05 -0800, Matt Broughton wrote: > I was testing the Gutenprint v5.2.14 against macos 10.14.2. I found that both a USB Epson WorkForce 1100 and a networked Xerox Phaser 6180 color laser printer were fine. I did and do have a paper feed problem with my Epson printer that is posted in another thread, but that doesn't impact the fact that Gutenprint drivers work fine in macos 10.14.2. > > I don't have any Canon printers to test, but there seems to be enough questions about the working of Canon printers I thought I would take a look to make sure that the gutenprint52+usb backend was included in the macos release. The answer was a surprising no., It is not included. There is a symlink -- > /usr/libexec/cups/backend/gutenprint52+usb -> /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/gutenprint52+usb > The actual executable, however, was never installed. > if test -f /Library/Printers/Gutenprint.printerDriver/Contents/MacOS/gutenprint52+usb ; then echo good file ; else echo no file here; fi > This returns "no file here" > > The scripts in the macosx directory in git shows that LIBUSB should be built and therefore picked up when ./configure is run. Might it be that LIBUSB never made it into the $PATH? > > Not having that backend would certainly cause problems problems for some users. So do we need to do a new release (5.2.15) for this? Also, can we get a build for 5.3? I'd like to do another 5.3 release and would really like a Mac release for it. -- Robert Krawitz <rl...@al...> *** MIT Engineers A Proud Tradition http://mitathletics.com *** Member of the League for Programming Freedom -- http://ProgFree.org Project lead for Gutenprint -- http://gimp-print.sourceforge.net "Linux doesn't dictate how I work, I dictate how Linux works." --Eric Crampton |
137 messages has been excluded from this view by a project administrator.
