This bug was fixed in the package cups - 1.4.6-5
---
cups (1.4.6-5) unstable; urgency=low
[ Till Kamppeter ]
* debian/patches/cups-avahi.dpatch: Updated the patch to add Avahi support
to the newest state of the art from
http://twaugh.fedorapeople.org/cups-avahi/ (upstream
** Branch linked: lp:debian/cups
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/295536
Title:
cups-pdf fails bad status reported and no pdf created
--
ubuntu-bugs mailing list
** Branch linked: lp:~pitti/cups/debian-trunk
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/295536
Title:
cups-pdf fails bad status reported and no pdf created
--
ubuntu-bugs mailing list
*throws hands into the air* I guess we just have to give up trying to
beat any sense into cups-pdf :/ Yes, I'll add it.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/295536
Title:
cups-pdf fails
Fixed in bzr.
** Changed in: cups (Ubuntu)
Status: New = Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/295536
Title:
cups-pdf fails bad status reported and no pdf created
--
I had this problem with Karmic. Adding
capability dac_read_search,
To the app armor profile fixed it for me. I should note that my profile
already had the following in it:
# unfortunate, but required for when $HOME is 700
capability dac_override,
I believe (but am not certain) that
Reopening the issue for CUPS, as per #75.
** Changed in: cups (Ubuntu)
Status: Fix Released = New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/295536
Title:
cups-pdf fails bad status
pitti, can you update the AppArmor profile according to comment #75?
Thanks.
** Changed in: cups (Ubuntu)
Assignee: (unassigned) = Martin Pitt (pitti)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
cups-pdf broke during upgrade from 8.10 to 9.04.
Bruno MACADRE fix in #38 works for me, but still can't print to file
with PDF selected.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of
I made a clean install of Karmic RC and the pdf is created normally (but
with 600 as file permission).
** Changed in: cups-pdf (Ubuntu)
Status: New = Invalid
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification
A faster but transient solution to this problem is to put apparmor into
complain mode, like this:
$ sudo aa-complain /usr/sbin/cupsd
I believe that change will last only until the next restart of apparmor
and cupsd.
--
cups-pdf fails bad status reported and no pdf created
Just upgraded from Jaungty to Karmic Alpha-5 by update-manager -d.
ii cups-pdf 2.5.0-4PDF printer for CUPS
ii cups 1.4.0-3.1 Common UNIX Printing System(tm) - server
The phenomenon is what I'm tried to print with cups-pdf printer, nothing
will show up in ~/PDF
Odd, I thought that we had fixed this when we updated the AppArmor
profile that comes with CUPS.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Ok, I believe I have solved this problem (at least in Jaunty as I
haven't tried in other versions).
1. run sudo nano /etc/apparmor.d/usr.sbin.cupsd
2. Add capability dac_read_search, (no quotes and don't forget the comma at
the end)
NOTE: It MUST be in the /usr/lib/cups/backend/cups-pdf section
** Changed in: cups
Status: New = Invalid
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Had same problem (9.04). did the following (don't know which one helped):
1. Added a folder named ${HOME}/PDF.
2. chmod 755 ${home}/PDF
3. sudo apt-get remove cups-pdf
4. sudo apt-get install cups-pdf
5. sudo aa-complain cupsd
after step 5 it worked, don't know if the earlier steps were
This worked for me:
Say you want the PDF output in: ~/pdfout123
1. mkdir ~/pdfout123
2. go root with sudo su
3. change the out-line in /etc/cups/cups-pdf.conf to: Out ${HOME}/pdfout123
4. change the two lines in /etc/apparmor.d/usr.sbin.cupsd to:
@{HOME}/pdfout123/ rw, and @{HOME}/pdfout123/*
** Also affects: cups
Importance: Undecided
Status: New
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing
I think I found a solution (or at least one other thing to fix). I ran the
command:
sudo chmod +s /usr/lib/cups/backend/cups-pdf
and it started working for me. There's been plenty of other chmod commands
listed above for this file, but none that did a set user ID. So just add it
to the
Making the backend suid is actually a security risk. We cannot recommend
this as a solution.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Well, it's either set suid and make it *WORK*, or don't set it and it's
broken. Until someone can make it work *without* having to hack it,
that's the solution.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification
Well, I've tried all the fixes in this thread (Jaunty/9.04), and STILL no
working cups-PDF. Forced uninstall/reinstall (purging out all settings),
setting permissions, setting AppArmor, etc. Nada, squat, nothing.
Have even checked that I had Ghostscript installed (suggested elsewhere).
This is a duplicate of bug 224365. Unfortunately I cannot mark it as
such, since bug 294929 is already a duplicate of this one, but I can't
seem to see bug 294929.
It was fixed in Karmic in
cups (1.3.10-4) unstable; urgency=low
* Add ghostscript-cups dependency. (LP: #385606)
*
https://wiki.ubuntu.com/DebuggingApparmor
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Is this bug fixed in Karmic?
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
As we noticed, this is an AppArmor issue and the AppArmor profile for
cups-pdf ships with CUPS, so we're invalidating the CUPS-PDF part of
this bug.
** Changed in: cups-pdf (Ubuntu)
Status: Confirmed = Invalid
--
cups-pdf fails bad status reported and no pdf created
BTW, sudo chmod 777 /usr/lib/cups/backend/cups-pdf is VERY VERY VERY
VERY wrong! Please don't change permissions on those backends if you
don't know for sure what that does. First you have a world-writable file
in your system now which anyone can tamper with to create a local root
exploit, and
Px means protected by a profile, we ship one for cups-pdf. Ux
means unlimited, i. e. there is no AppArmor confinement whatsoever for
cups-pdf. See man apparmor.d.
Indeed you need world-executable permissions on your home directory
nowadays (just like with apache, etc.). We install home
Indeed, so changing the cups-pdf section in the cupsd AppArmor profile
is the wrong answer. This then points to possible regressions in
AppArmor, on an existing configuration that, until Intrepid, worked out
of the box.
I'm thus reassigning this to apparmor.
--
cups-pdf fails bad status
MaxFox's suggestion (comment #32) did not work for me. In addition, no
amount of file permission changes worked for me. I am using Ubuntu 9.04
x86_64 (2.6.28-11-generic #42-Ubuntu SMP).
However, the following did work. I changed the line #85 in
/etc/apparmor.d/usr.sbin.cupsd
-
I'd really like to hear more about what this change from P to U implies,
from a security perspective, especially given how these very same
settings were working fine until Intrepid. For all we know, something
changed in the kernel's security model that might have introduced
regressions, while our
** Also affects: apparmor (Ubuntu)
Importance: Undecided
Status: New
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
MaxFox's suggestion worked. I could not add New cups PDF printer to new
Jaunty install until following his steps.
1. remove PDF printer from administration-printing
2. remove cups-pdf via administration-synaptic package manager
3. remove PDF folder in your home folder
4. create PDF folder in your
right, still existing in Jaunty and the setting it to complain mode
fixed it.
There should be a fix for this since users don't always google for bugs
and I'm sure it'll turn them off.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received
Defect exists in Ubuntu 9.04.
I am NOT able to work-around this using the uninstall/reinstall
procedure mentioned in above thread.
I AM able to work around this using François Letendre solution of:
$ sudo aa-complain cupsd
--
cups-pdf fails bad status reported and no pdf created
The workaround definitely works and AppArmor should print out logs of
the offending operation... but where are the logs?
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs,
Thanks.
Simply running this solved the problem.
$ sudo aa-complain cupsd
The ~/PDF folder was then automatically created when I printed to pdf.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a
In my Ubuntu 9.04, I had to do sudo aa-complain cupsd. Now it works
ok.
/usr/lib/cups/backend/cups-pdf:
-rwx-- 1 root root 21976 2009-02-14 22:47 cups-pdf
/home/krzysiek:
drwx-- 86 krzysiek krzysiek 12288 2009-05-04 16:24
~/PDF folder was created automatically with the following
Just upgraded to 9.04 from 8.10.
/usr/lib/cups/backend/cups-pdf permissions:
-rwx-- 1 root root 21976 2009-02-14 23:47 cups-pdf
home folder permissions:
drwxr-x--x 115 george george 4096 2009-04-26 12:54 george
PDF folder inside home folder permissions:
drwxr-x--- 2 george george 4096
Problem in 9.04 resolved by creating ~/user/PDF and running $ sudo aa-complain
cupsd
This trips up nearly every newbie, and whilst it may be an early right of
passage, it would be nice if this were finally updated as default. It turns new
people off of Ubuntu and the energy used in this and
Actually, as long as Execute permissions exist on ${HOME}, the CUPS-PDF
backend should be able to create ${HOME}/PDF itself if it's not there.
This means that having either 711 or 751 permissions on ${HOME} should
be enough.
--
cups-pdf fails bad status reported and no pdf created
After checking with Ubuntu developers and CUPS maintainers, it appears
that default home directory permissions when adding new users is 755, so
this should work for default installations. If it doesn't, we'd like to
hear more details.
In other cases, as long as group Others has Execute
Mariusz: Jaunty repositories are frozen at the moment.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I still have this problem on 9.04. It is a very short time to final
release of Jaunty.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Bruno M's solution worked well for me.
As a word of warning, if you've changed the output path in cups-
pdf.conf, you need to make sure that the path in the
/usr/lib/cups/backend/cups-pdf section of /etc/apparmor.d/usr.sbin.cupsd
is updated too
e.g. change @{HOME}/PDF and @{HOME}/PDF/* to the
The Jaunty RC still has this problem, as far as I can see.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Bruno M's explanation works for me as well, and is surely much more
secure than my first solution.
Could someone integrate it in the next version of cups?
Thanks, Eric
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug
Hi !
Like Eric says, it's a problem in the AppArmor configuration. His
workaround works well but it remove the protection over cups-pdf. Like
we see in the dmesg posted by marcobra it looks like a capabilities
problem for /usr/lib/cups/backend/cups-pdf :
---
[89144.961555] type=1503
Eric L.'s fix to /etc/apparmor.d/usr.sbin.cupsd
and a restart of AppArmor fixed it on my system
Neither reinstalling cups-pdf nor messing with $HOME/PDF did any good.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug
aptitude reinstall cups-pdf worked for me
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
running: sudo aa-complain cupsd fixed it for me. so it doesnt seem to be
an issue of cups-pdf actually
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
I'd just reinstalled my Ubunto and now I have a 8.10 version on an amd64
machine.
The solution from Le Gluon Du Net, as confirmed by others here, worked
very well to me.
Thank you all.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received
Thank you jellis47 and MaxFox, your solution worked for me.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
confirming jellis47 solution
1. remove PDF printer from administration-printing
2. remove cups-pdf via administration-synaptic package manager
3. remove PDF folder in your home folder
4. create PDF folder in your home folder
5. install cups-pdf via administration-synaptic package manager
--
Eric: This should be the same as running sudo aa-complain cups or sudo
aa-complain cups-pdf.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I'm pretty sure that it's not a bug in cups-pdf but a bug in the
AppArmor configuration for cups-pdf.
Workaround (and proof that it's an AppArmor configuration issue):
open the file /etc/apparmor.d/usr.sbin.cupsd
and edit the line:
/usr/lib/cups/backend/cups-pdf {
in order to get:
I have spent some time with this bug my solution was to remove cups-pdf, then
create a directory ~/PDF.
I then reinstalled cups-pdf and was able to print to pdf first time.
I didn't have to change permissions on /usr/lib/cups/backend/cups-pdf or ~/PDF
this time. it just worked. Hope this helps.
I have the same problem: trying to print a pdf in Ubuntu 8.10 gives the
error message usr/lib/cups/backend/cups-pdf failed.
Changing the permission to o+x of my home directory solves this problem.
But after changing it back to o-x the problem comes back.
Under Ubuntu 8.04 everything worked well.
I have the same problem, can't print with cups-pdf printer in ubuntu 8.10
It returns failed when i try to run a test page, even with 777 rights on
/home/user/PDF
Thanks for a solution
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received
Chmoding ~ to 711 worked for me too. I wonder why cups need to enter ~
but not to write in ~/PDF...
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Actually, printing into pdf only works for me if my ~ is 711 *and*
/usr/lib/cups/backend/cups-pdf is suid (4755). The permissions for my
home dir don't solve the problem by themselves, and neither does chgrp-
ing ~/PDF to lp and adding myself to the lp group.
--
cups-pdf fails bad status
Confirmed. The following workaround even with PDF as a symlink to an
encrpyted Private/PDF :)
$ sudo aa-complain cupsd
Setting /etc/apparmor.d/usr.sbin.cupsd to complain mode.
Thanks, Le Gluon Du Net.
--
cups-pdf fails bad status reported and no pdf created
Thank you, Le Gluon Du Net. That workaround worked for me, and I have my
PDF folder as a systemlink to a folder on another partition.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of
I had the same problem.
Following works for me:
mkdir ~/PDF
chmod 777 ~/PDF
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
I've had the same problem (Intrepid). I already had the PDF directory
(755) from Hardy. My workaround: chmod 711 ~, do print to PDF, then
chmod 700 ~ again.
I think that there are two connected problems.
1) cups-pdf fails to create PDF directory (bug #295318)
2) cups-pdf cannot navigate to PDF
To clarify, I think that this bug affects those who have home directory
permissions of 700 or similar. Those who fixed the problem by just
creating ~/PDF really want bug #295318.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug
for me only this command solved the problem:
sudo aa-complain cupsd
after that command, I printed a pdf, the PDF folder appear in my HOME
folder with the pdf inside.
LGDN
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug
I confirm bug with /usr/lib/cups/backend/cups-pdf failed status.
I have 755 on /home/username.
I have no PDF folder, or manually created PDF with permissions 700, in both
cases I got same error.
In Ubuntu 8.04 its work without any manual tricks.
--
cups-pdf fails bad status reported and no pdf
chmod 777 on (manually created) PDF fixes it, i now able to get nice
PDFs.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs
jpkotta (and developers): But a permission of 755 on $home ( I suppose
you mean /home/username/ folder) would give other people the right to
access my home folder and its content.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this
711 should be enough for /home/jpkotta to get files.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I got it to work. I changed the permissions on $HOME. Permissions on
$HOME were 750. 755 works, 751 and 754 do not work. Permissions on
~/PDF are 700.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because
confirm same problem here, intrepid.
My ~/PDF/ is empty.
Printing a test page to the PDF printer via localhost:631, gives me this
new file:
$ find /var/spool/cups-pdf/
/var/spool/cups-pdf/
/var/spool/cups-pdf/SPOOL
/var/spool/cups-pdf/ANONYMOUS
/var/spool/cups-pdf/ANONYMOUS/Test_Page.pdf
$ lpr
Paul Sinnett:
/var/log/cups/cups-pdf_log is empty
ls -ld /home/user/
drwxrwx--- 71 user user 4096 2008-12-03 20:21 /home/user/
ls -l /home/user/PDF/
yhteensä 0 (yhteensä=total)
ls -ld /home/user/PDF/
drwxr-xr-x 2 user user 4096 2008-11-14 20:34 /home/user/PDF/
--
cups-pdf fails bad status
what does your /var/log/cups/cups-pdf_log say?
if it says [ERROR] failed to create directory (/home/username/PDF)
then your home directory possibly lacks the permissions required by
cups-pdf
try:
ls -l /home
to check the permissions on your users' directories
--
cups-pdf fails bad status
[EMAIL PROTECTED]:~$ ls -ld /home/rossg
drwxr-xr-x 85 rossg rossg 4096 2008-11-29 23:28 /home/rossg
[EMAIL PROTECTED]:~# ls -l /home/rossg/PDF
lrwxrwxrwx 1 rossg rossg 11 2008-11-10 11:35 /home/rossg/PDF - Private/PDF
[EMAIL PROTECTED]:~# tail /var/log/cups/cups-pdf_log
Sun Nov 30 08:21:25 2008
Confirming here also (Intrepid) . Using Intrepid, attempting to print to
PDF logged as a normal user in KDE causes « (/usr/lib/cups/backend/cups-
pdf) stopped with status 5! » and no PDF is generated.
However, using the CUPS web interface (http://localhost:631), logged
there as root, trying to
I think I have the same issue. I cannot add a PDF printer in the printer
configuration tool.
But the 'print to file' option works with pdf and ps formats.
Starting cups thru terminal results in error message:
[EMAIL PROTECTED]:~$ sudo /etc/init.d/cups start
* Starting Common Unix Printing
I can confirm the above mentioned bug on my Ubuntu 8.10 (Intrepid).
I also changed permissions on /usr/lib/cups/backend/cups-pdf with:
sudo chmod 755 /usr/lib/cups/backend/cups-pdf
and made the failed status on the printing window go away as marcobra
did.
I created the PDF folder in my home
I can also confirm this, with the same results as papukaija.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
For me cups-pdf worked with Ubuntu 8.04 (Hardy), but after the upgrade
to Intrepid, the cups-pdf hasn't worked.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is
I can confirm this bug with same problems: it show a
/usr/lib/cups/backend/cups-pdf failed status into printing window (or
from localhost:631)
/var/log/cups/error_log :
(/usr/lib/cups/backend/cups-pdf) stopped with status 5!
** Changed in: cups-pdf (Ubuntu)
Status: New = Confirmed
--
*** This bug is a duplicate of bug 295318 ***
https://bugs.launchpad.net/bugs/295318
** This bug has been marked a duplicate of bug 295318
cups pdf ubuntu 8.10
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug
I think is NOT a duplicate of
https://bugs.launchpad.net/ubuntu/+source/cups-pdf/+bug/295318
because it doesn't work even if i create a PDF dir under my home directory...
Thank you
** This bug is no longer a duplicate of bug 295318
cups pdf ubuntu 8.10
** Description changed:
Binary
I confirm this bug as i got the same problem.
Ubuntu: 8.10 x86
cups-pdf : 2.4.8-1ubuntu1
see https://answers.launchpad.net/ubuntu/+source/cups-
pdf/+question/50656
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug
I confirm this in my Intrepid Ibex.
--
cups-pdf fails bad status reported and no pdf created
https://bugs.launchpad.net/bugs/295536
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
86 matches
Mail list logo
