Prev: [cotvnc] non-us keyboards, appeal to developers
Next: LAN (Windows 7 and Snow Leopard)
From: Tom Stiller on 6 Apr 2010 20:03
In article <4bbb8379$0$4871$9a6e19ea(a)unlimited.newshosting.com>,
Father Walt <Walt(a)bitbucket.com> wrote:

> Does anyone here have CUPS-PFD working on Snow Leopard ?? I've tried
> every hint that has been provided by the development community, and I
> just can't seem to get it to work at all. I can "print" to cups-pdf,
> but nothing shows up in the folder, or on my system, anywhere. I've
> reinstalled, the software many times, and the SL a few times already.
> That's one piece of software I really miss when I went to SL. Any
> ideas ???
>
> -- Father Walt
> The faulty interface lies between the chair and the keyboard.

Yes. See <http://www.codepoetry.net/projects/cups-pdf-for-mosx> for
details.

--
Tom Stiller

PGP fingerprint = 5108 DDB2 9761 EDE5 E7E3 7BDA 71ED 6496 99C0 C7CF
From: Richard Maine on 7 Apr 2010 02:19
Chris Schram <schram(a)webenet.net> wrote:

> From the site
> <http://www.codepoetry.net/2009/09/03/cupspdf_is_broken_in_snow_leopard>:
>
> CUPS-PDF is broken in Snow Leopard...

Note that message is 7 months old. From that same page, click on
products, then the more-info link under CUPS-PDF.

--
Richard Maine | Good judgment comes from experience;
email: last name at domain . net | experience comes from bad judgment.
domain: summertriangle | -- Mark Twain
From: David Empson on 7 Apr 2010 03:39
Richard Maine <nospam(a)see.signature> wrote:

> Chris Schram <schram(a)webenet.net> wrote:
>
> > From the site
> > <http://www.codepoetry.net/2009/09/03/cupspdf_is_broken_in_snow_leopard>:
> >
> > CUPS-PDF is broken in Snow Leopard...
>
> Note that message is 7 months old. From that same page, click on
> products, then the more-info link under CUPS-PDF.

The suggestion solution on that page (sudo chmod 700 on the backend
file, and manually creating ~/Desktop/cups-pdf) doesn't work.

I have established that the job gets as far as the print queue (if
paused), but the PDF doesn't appear.

I tried reinstalling CUPS-PDF, as it looks like my Snow Leopard
installation had deleted /etc/cups/cups-pdf.conf, and did the chmod
again, but that didn't help.

The obvious clue - each print attempt has an error in system.log like
this:

sandboxd[5078]: pstopdf(5077) deny file-write*
/Users/dempson/Desktop/cups-pdf/job_NNN-title.pdf

For some reason, pstopdf (invoked by cups-pdf) is being sandboxed, and
doesn't have permission to write files (at least, not in my home
directory).

The most likely explanation is that CUPS itself is sandboxing some or
all backends (including cups-pdf) and denying them permission to write
files.

A little reading up on sandboxing and CUPS configuration didn't reveal
anything obvious.

No, it isn't a folder permissions issue - I reconfigured CUPS to use a
world-writeable folder in my home directory and that didn't help.


Anyone else had any luck getting CUPS-PDF to work on Snow Leopard?
--
David Empson
dempson(a)actrix.gen.nz
From: JF Mezei on 7 Apr 2010 03:48
David Empson wrote:

> sandboxd[5078]: pstopdf(5077) deny file-write*
> /Users/dempson/Desktop/cups-pdf/job_NNN-title.pdf

I am not an expert by any means with this. Under what userID does the
CUPS-PDF run ? If it runs under its own user id, it may not have
privileges to write into your directory.

You could find out what username it uses, and grant that username read
write execute on the cups-pdf directory in your account.
From: David Empson on 7 Apr 2010 04:52
JF Mezei <jfmezei.spamnot(a)vaxination.ca> wrote:

> David Empson wrote:
>
> > sandboxd[5078]: pstopdf(5077) deny file-write*
> > /Users/dempson/Desktop/cups-pdf/job_NNN-title.pdf
>
> I am not an expert by any means with this. Under what userID does the
> CUPS-PDF run ? If it runs under its own user id, it may not have
> privileges to write into your directory.

It is not a privileges problem, as I already noted. I told cups-pdf to
use a folder which had permssions of 777 (and was in an accessible
location), and it still got the same error.

The sandbox mechanism allows a process (and anything it spawns) to be
denied certain access rights, independently of ACLs, permissions, etc.,
even if the process is running as root.

In this case it appears that cups-pdf has been sandboxed to deny
permission to write any files (or possibly "no writes except
temporary"). I expect CUPS is doing that, but I don't know what its
criteria are for doing so.

Best documentation I've found on sandboxing:

man sandbox_init

> You could find out what username it uses, and grant that username read
> write execute on the cups-pdf directory in your account.

Won't help. If it can't write to a 777 folder, it doesn't make any
difference which user it is.

--
David Empson
dempson(a)actrix.gen.nz
 | 
Pages: 1
Prev: [cotvnc] non-us keyboards, appeal to developers
Next: LAN (Windows 7 and Snow Leopard)