[Bug 1971242] Re: printing PDF appears always grey, no color
Marc, thanks a lot for completing this one, as it has badly coincided with my trip to India. And sorry for having let anyone to wait so long ... -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to okular in Ubuntu. https://bugs.launchpad.net/bugs/1971242 Title: printing PDF appears always grey, no color To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1971242] Re: printing PDF appears always grey, no color
** Description changed:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers are
affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
- FiileDevice Yes
+ FileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-PDF_Printer-
PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
editor. Check whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints about
color printing. So the regression potential is very low.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to okular in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1971242] Re: printing PDF appears always grey, no color
@ahasenak, I have uploaded an SRU for this bug for Lunar right now. As soon as it gets approved, please test it as described in the initial description (there is an option to do it without an affected printer) and report back here. I will not upload an SRU for Kinetic, as this version is already EOL. ** Also affects: okular (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: atril (Ubuntu Lunar) Importance: Undecided Status: New ** No longer affects: atril (Ubuntu Lunar) ** No longer affects: okular (Ubuntu Lunar) ** Changed in: cups (Ubuntu Lunar) Importance: Undecided => High ** Changed in: cups (Ubuntu Lunar) Status: New => In Progress -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to okular in Ubuntu. https://bugs.launchpad.net/bugs/1971242 Title: printing PDF appears always grey, no color To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1971242] Re: printing PDF appears always grey, no color
Thank you very much. Marking the SRU for Jammy as verified ... ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to okular in Ubuntu. https://bugs.launchpad.net/bugs/1971242 Title: printing PDF appears always grey, no color To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1971242] Re: printing PDF appears always grey, no color
** Description changed:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
[ Impact ]
If the PPD file for a printer has a ColorModel option and the only
choice in it for printing in color is not named RGB but CMYK instead,
the printer cannot be made printing in color with intuitive methods,
usually selcting the color choice in the print dialog (which makes
ColorModel=CMYK be sent along with the job).
Only an ugly command-line-based workaround, running the command
lpadmin -p PRINTER -o print-color-mode-default=color
makes the printer print in color.
An example for printers with such PPDs are printers from RICOH and OEM
(Lanier, InfoTec, Savin, ..), so many high-end color laser printers are
affected.
[ Test Plan ]
Remove the workaround if you had applied it:
lpadmin -p PRINTER -R print-color-mode-default
If you have an affected printer, print a PDF file (or use the print
functionality in an application) with colored content and choose the
setting for color printing in the print dialog. When printing via
command line do
lp -d PRINTER -o ColorModel=CMYK FILE.pdf
Without the SRU applied you will get a grayscale/monochrome printout,
with it applied, you will get a colored printout.
To test without a printer:
Stop CUPS:
sudo systemctl stop cups
Edit /etc/cups/cups-files.conf to have a line
FiileDevice Yes
and start CUPS again:
sudo systemctl start cups
Then create a queue using the attached sample PPD file:
lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-PDF_Printer-
PDF.ppd
Print a file to this queue as described above. When the job is done
("lpstat" does not show it any more), open /tmp/printout with a text
- editor. Chcke whether it contains a line
+ editor. Check whether it contains a line
@PJL SET RENDERMODE=COLOR
near its beginning, and NOT a line
@PJL SET RENDERMODE=GRAYSCALE
[ Where problems could occur ]
The patches are simple and they are also for some time in newer CUPS
versions (2.4.2 and newer) which are included in several distributions
(Ubuntu 22.10, 23.04, and others) and did not cause any complaints about
color printing. So the regression potential is very low.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to okular in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1971242] Re: printing PDF appears always grey, no color
Fixed in Mantic via cups 2.4.5-0ubuntu1: cups (2.4.5-0ubuntu1) mantic; urgency=medium * Update to new upstream version 2.4.5. - Fixes color printing on printers with "CMYK" choice instead of "RGB" in "ColorModel" option of their PPD (Upstream issues #451 and #500, LP: 1971242). * Merge from Debian unstable. Remaining changes: - Added "--enable-snapped-clients" to the "./configure" options to use the correct Snap mediation mode for an unsnapped cupsd, like provided by this package. - In the AppArmor profile allow CUPS to access (/var)/run/snapd.socket to allow cupsd to determine which interfaces a snapped client is plugging. - Build-depend on libapparmor-dev, libsnapd-glib-dev, needed for Snap mediation. - Added fully automatic generation of PPD option setting presets to be applied depending on the settings of the job IPP attributes "print-color-mode", "print-quality", and "print-content-optimize". This allows easy control of any printer with only standard IPP attributes, as for example from a phone (functionality overtaken from cups-filters, mot (yet) upstream in CUPS). - In debian/rules updated ./configure arguments from --enable-gnutls to --with-tls=gnutls. Now libcups has support for all hash types again, especially can provide sha2-256 to PAPPL. - When polling capabilities of a driverless printer via get-printer-attributes IPP request, do a separate poll of the media-col-database attribute in case it did not get obtained by the first polls. - In libcupsimage2 recommend libcupsfilters2 instead of libcupsfilters1. * Manually refreshed patch 9100-ppd-cache-add-auto-presets.patch. * Removed patches included upstream: - 9110-create-local-printer-localhost-fix.patch - CVE-2022-26691-2.patch - snapd-glib-2.patch - poll-media-col-database-separately.patch - CVE-2023-32324.patch cups (2.4.2-4) unstable; urgency=medium * CVE-2023-32324 A heap buffer overflow vulnerability would allow a remote attacker to lauch a dos attack. ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2022-26691 ** CVE added: https://cve.mitre.org/cgi-bin/cvename.cgi?name=2023-32324 ** Changed in: cups (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to okular in Ubuntu. https://bugs.launchpad.net/bugs/1971242 Title: printing PDF appears always grey, no color To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1971242] Re: printing PDF appears always grey, no color
Uploaded CUPS 2.4.5 to Mantic. This version has the mentioned fixes included. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to okular in Ubuntu. https://bugs.launchpad.net/bugs/1971242 Title: printing PDF appears always grey, no color To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1971242] Re: printing PDF appears always grey, no color
** Changed in: cups (Ubuntu Lunar) Status: New => In Progress ** Changed in: cups (Ubuntu) Status: Confirmed => Fix Committed ** Also affects: okular (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Jammy) Importance: Undecided Status: New ** Also affects: atril (Ubuntu Jammy) Importance: Undecided Status: New ** No longer affects: cups (Ubuntu Lunar) ** Changed in: cups (Ubuntu Jammy) Importance: Undecided => High ** Changed in: cups (Ubuntu Jammy) Status: New => In Progress ** No longer affects: okular (Ubuntu Lunar) ** No longer affects: okular (Ubuntu Jammy) ** No longer affects: atril (Ubuntu Lunar) ** No longer affects: atril (Ubuntu Jammy) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to okular in Ubuntu. https://bugs.launchpad.net/bugs/1971242 Title: printing PDF appears always grey, no color To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1971242] Re: printing PDF appears always grey, no color
Sample PPD file for the SRU test plan.
** Description changed:
After upgrading from 20.04 LTS to 22.04 LTS I can't print colored PDF
document. The print appears always b/w regardless color printing was
enabled or not. Printing from LibreOffice produces a color print. This
behavior (bug) is reproducible on three upgraded machines. It would be
nice to have color print back again.
+
+ [ Impact ]
+
+ If the PPD file for a printer has a ColorModel option and the only
+ choice in it for printing in color is not named RGB but CMYK instead,
+ the printer cannot be made printing in color with intuitive methods,
+ usually selcting the color choice in the print dialog (which makes
+ ColorModel=CMYK be sent along with the job).
+
+ Only an ugly command-line-based workaround, running the command
+
+ lpadmin -p PRINTER -o print-color-mode-default=color
+
+ makes the printer print in color.
+
+ An example for printers with such PPDs are printers from RICOH and OEM
+ (Lanier, InfoTec, Savin, ..), so many high-end color laser printers are
+ affected.
+
+ [ Test Plan ]
+
+ Remove the workaround if you had applied it:
+
+ lpadmin -p PRINTER -R print-color-mode-default
+
+ If you have an affected printer, print a PDF file (or use the print
+ functionality in an application) with colored content and choose the
+ setting for color printing in the print dialog. When printing via
+ command line do
+
+ lp -d PRINTER -o ColorModel=CMYK FILE.pdf
+
+ Without the SRU applied you will get a grayscale/monochrome printout,
+ with it applied, you will get a colored printout.
+
+ To test without a printer:
+
+ Stop CUPS:
+
+ sudo systemctl stop cups
+
+ Edit /etc/cups/cups-files.conf to have a line
+
+ FiileDevice Yes
+
+ ans start CUPS again:
+
+ sudo systemctl start cups
+
+ Then create a queue using the attached sample PPD file:
+
+ lpadmin -p color-test -E -v file:/tmp/printout -P Ricoh-PDF_Printer-
+ PDF.ppd
+
+ Print a file to this queue as described above. When the job is done
+ ("lpstat" does not show it any more), open /tmp/printout with a text
+ editor. Chcke whether it contains a line
+
+ @PJL SET RENDERMODE=COLOR
+
+ near its beginning, and NOT a line
+
+ @PJL SET RENDERMODE=GRAYSCALE
+
+ [ Where problems could occur ]
+
+ The patches are simple and they are also for some time in newer CUPS
+ versions (2.4.2 and newer) which are included in several distributions
+ (Ubuntu 22.10, 23.04, and others) and did not cause any complaints about
+ color printing. So the regression potential is very low.
** Attachment added: "Ricoh-PDF_Printer-PDF.ppd"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1971242/+attachment/5679703/+files/Ricoh-PDF_Printer-PDF.ppd
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to okular in Ubuntu.
https://bugs.launchpad.net/bugs/1971242
Title:
printing PDF appears always grey, no color
To manage notifications about this bug go to:
https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions
--
kubuntu-bugs mailing list
kubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1971242] Re: printing PDF appears always grey, no color
** Also affects: okular (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: cups (Ubuntu Lunar) Importance: Undecided Status: New ** Also affects: atril (Ubuntu Lunar) Importance: Undecided Status: New ** Changed in: cups (Ubuntu Lunar) Importance: Undecided => High -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to okular in Ubuntu. https://bugs.launchpad.net/bugs/1971242 Title: printing PDF appears always grey, no color To manage notifications about this bug go to: https://bugs.launchpad.net/cups/+bug/1971242/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1877528] Re: Applet does not terminate at end of X desktop session
The upstream author has tested and found out that the problem only occurs with lightdm and not with gdm as desktop manager, especially the ones showing the problem are sddm, kdm, lightdm and the ones not showing the problem are gdm and lxdm. Adding desktop manager tasks ... See this comment and following: https://github.com/OpenPrinting/system-config- printer/issues/175#issuecomment-627771765 ** Also affects: lightdm (Ubuntu) Importance: Undecided Status: New ** Also affects: sddm (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to sddm in Ubuntu. https://bugs.launchpad.net/bugs/1877528 Title: Applet does not terminate at end of X desktop session To manage notifications about this bug go to: https://bugs.launchpad.net/system-config-printer/+bug/1877528/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1348384] Re: evince and okular do not render eps files correctly resulting in a black background
The SRU was the simple application of an upstream patch from this upstream bug report https://bugs.freedesktop.org/show_bug.cgi?id=76450 I do not know anything of the internals of libspectre and even do not have upload rights for it, as it does not belong to printing. It is used by evince to generate certain output data formats. I only have done the debdiff for that SRU because no one else did it. I am not maintaining libspectre in Ubuntu. So my suggestion is to simply remove the patch if the solution of the current problem is urgent and no better patch from upstream is available. But take into account that the problem of the original SRU will reappear. Let this be a new SRU. Wait for a better upstream fix if it is not so urgent. In general make upstream aware of both problems and that fix of the first problem caused the second and what is needed is a fix to solve both problems. Do another SRU if the final fix is available. ** Changed in: libspectre (Ubuntu Trusty) Assignee: Till Kamppeter (till-kamppeter) => (unassigned) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to libspectre in Ubuntu. https://bugs.launchpad.net/bugs/1348384 Title: evince and okular do not render eps files correctly resulting in a black background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libspectre/+bug/1348384/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1348384] Re: evince and okular do not render eps files correctly resulting in a black background
Marek, is the patch from upstream (or at least submitted to upstream)? Can we expect it to be included in an upstream version of libspectre soon? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to okular in Ubuntu. https://bugs.launchpad.net/bugs/1348384 Title: evince and okular do not render eps files correctly resulting in a black background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1348384/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1348384] Re: evince and okular do not render eps files correctly resulting in a black background
Marek, it seems that your fix on libspectre for bug 1242678 is causing this bug. Can you have a look? Thanks. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to okular in Ubuntu. https://bugs.launchpad.net/bugs/1348384 Title: evince and okular do not render eps files correctly resulting in a black background To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1348384/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 688640] Re: Kubuntu - Can't Configure Printer via "system-config-printer-kde"
According to the debian/changelog this package has moved to kdeadmin, so moving the bug appropriately. ** Package changed: system-config-printer-kde (Ubuntu) => kdeadmin (Ubuntu) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdeadmin in Ubuntu. https://bugs.launchpad.net/bugs/688640 Title: Kubuntu - Can't Configure Printer via "system-config-printer-kde" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdeadmin/+bug/688640/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1355136] Re: Add recommends printer-driver-brlaser package in -desktop installations
brlaser is now promoted to Main. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1355136 Title: Add recommends printer-driver-brlaser package in -desktop installations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1355136/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1355136] Re: Add recommends printer-driver-brlaser package in -desktop installations
Manually confirming, as the "Does this bug affect you?" facility is currently down (times out). -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1355136 Title: Add recommends printer-driver-brlaser package in -desktop installations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1355136/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1355136] Re: Add recommends printer-driver-brlaser package in -desktop installations
I have now done a MIR of said package (bug 1359137). Can the addition to the seeds be done before Utopic FF? Thanks. ** Changed in: ubuntu-meta (Ubuntu) Status: New => Confirmed ** Changed in: ubuntustudio-meta (Ubuntu) Status: New => Confirmed ** Changed in: xubuntu-meta (Ubuntu) Status: New => Confirmed ** Changed in: ubuntu-gnome-meta (Ubuntu) Status: New => Confirmed ** Changed in: lubuntu-meta (Ubuntu) Status: New => Confirmed ** Changed in: kubuntu-meta (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1355136 Title: Add recommends printer-driver-brlaser package in -desktop installations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1355136/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1355136] Re: Add recommends printer-driver-brlaser package in -desktop installations
MIR for brlaser is approved. ** Changed in: kubuntu-meta (Ubuntu) Importance: Undecided => High ** Changed in: lubuntu-meta (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-gnome-meta (Ubuntu) Importance: Undecided => High ** Changed in: ubuntu-meta (Ubuntu) Importance: Undecided => High ** Changed in: ubuntustudio-meta (Ubuntu) Importance: Undecided => High ** Changed in: xubuntu-meta (Ubuntu) Importance: Undecided => High -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/1355136 Title: Add recommends printer-driver-brlaser package in -desktop installations To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kubuntu-meta/+bug/1355136/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1242678] Re: evince cannot render some EPS files
Here we need to agree with libspectre and evince upstream. The libspectre patch proposed for the SRU is from this upstream bug https://bugs.freedesktop.org/show_bug.cgi?id=76450 but they also tell that an additional fix on evince is needed, supplied as a patch on this bug https://bugzilla.gnome.org/show_bug.cgi?id=731786 To follow this, we should post a second SRU for evince (and let this go to -updates). -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to libspectre in Ubuntu. https://bugs.launchpad.net/bugs/1242678 Title: evince cannot render some EPS files To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1242678/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1242678]
Seb, you could use https://bugzilla.gnome.org/show_bug.cgi?id=710957 for this. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to libspectre in Ubuntu. https://bugs.launchpad.net/bugs/1242678 Title: evince cannot render some EPS files To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1242678/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1242678]
Seb, can you do an appropriate patch on evince and report a bug upstream? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to libspectre in Ubuntu. https://bugs.launchpad.net/bugs/1242678 Title: evince cannot render some EPS files To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1242678/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1229295] Re: A4 Right margin cut off with HP Deskjet 5550
Can you try the "A4 Small Margins" (A4.SM) page size? -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to okular in Ubuntu. https://bugs.launchpad.net/bugs/1229295 Title: A4 Right margin cut off with HP Deskjet 5550 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1229295/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 924233] Re: systemsettings crashed with NameError in _perform_authentication_with_dialog(): global name 'AuthDialog' is not defined
Harald, system-config-printer-kde was removed from Ubuntu years ago, the problem must be in some other component, probably in KDE's printer setup tool needing to be updated for recent API changes in system-config- printer. ** Package changed: system-config-printer-kde (Ubuntu) => kde-workspace (Ubuntu) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/924233 Title: systemsettings crashed with NameError in _perform_authentication_with_dialog(): global name 'AuthDialog' is not defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/924233/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 939694] Re: systemsettings crashed with AttributeError in save_printer(): 'cups.Connection' object has no attribute '_begin_operation'
Harald, system-config-printer-kde was removed from Ubuntu years ago, the problem must be in some other component, probably in KDE's printer setup tool needing to be updated for recent API changes in system-config- printer. ** Package changed: system-config-printer-kde (Ubuntu) => kde-workspace (Ubuntu) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/939694 Title: systemsettings crashed with AttributeError in save_printer(): 'cups.Connection' object has no attribute '_begin_operation' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/939694/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 978022] Re: systemsettings crashed with IndexError in on_tvNPDevices_cursor_changed(): list index out of range
Harald, system-config-printer-kde was removed from Ubuntu years ago, the problem must be in some other component, probably in KDE's printer setup tool needing to be updated for recent API changes in system-config- printer. ** Package changed: system-config-printer-kde (Ubuntu) => kde-workspace (Ubuntu) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/978022 Title: systemsettings crashed with IndexError in on_tvNPDevices_cursor_changed(): list index out of range To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/978022/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 978404] Re: systemsettings crashed with NameError in save_printer(): global name 'show_IPP_Error' is not defined
Harald, system-config-printer-kde was removed from Ubuntu years ago, the problem must be in some other component, probably in KDE's printer setup tool needing to be updated for recent API changes in system-config- printer. ** Package changed: system-config-printer-kde (Ubuntu) => kde-workspace (Ubuntu) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kde-workspace in Ubuntu. https://bugs.launchpad.net/bugs/978404 Title: systemsettings crashed with NameError in save_printer(): global name 'show_IPP_Error' is not defined To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kde-workspace/+bug/978404/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1082520] Re: Qt Print dialog needs to support Bonjour broadcasting of remote printers
Bug reported upstream as https://bugreports.qt-project.org/browse/QTBUG-28188 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/1082520 Title: Qt Print dialog needs to support Bonjour broadcasting of remote printers To manage notifications about this bug go to: https://bugs.launchpad.net/qt/+bug/1082520/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 1082520] [NEW] Qt Print dialog needs to support Bonjour broadcasting of remote printers
Public bug reported: CUPS upstream dropped the CUPS broadcasting/browsing mechanism to automatically discover shared remote printers beginning from 1.6.x. Replacement is Bonjour-based broadcasting odf the shared printers by CUPS and on the client side the application's print dialogs are responsible for browsing these broadcasts and listing the remote printers appropriately. CUPS even provides a library function for that now. See https://blueprints.launchpad.net/ubuntu/+spec/desktop-r-cups-bonjour- browsing I wrote there: -- The CUPS Browsing/Broadcasting mechanism which made print queues shared on remote CUPS servers automatically visible for the local CUPS daemon and so for local applications got dropped upstream from CUPS 1.6.x on. Ubpstream has replaced this functionality by Bonjour-based broadcasting (under Linux implemented via Avahi), an OS-indpendent PWG (Printing Working Group) standard, but this lacks the implementation of browsing on the client side making the printers on remote CUPS servers not automatically appearing any more. Ubuntu Quantal's CUPS has a mega patch to forward-port this functionality from the old CUPS for one cycle, to avoid regressions. We cannot carry such a patch eternally, and we should follow upstream and the PWG standards. So in Ubuntu Raring we need the real solution which means that the print dialogs (upstream-recommended solution) or the CUPS daemon (how I like to have it) takes the new Bonjour (Avahi) broadcasts to display the shared remote CUPS queues automatically. The browsing functionality is implemented in the CUPS library (libcups) from CUPS 1.6.x on, but there is currently no production code using these functions. Upstream expects the print dialogs to use the new library functions for displaying the new queues. This would require modifications and upstream submissions for GTK, Qt, and LibreOffice at least and this does not safely cover all existing applications which have CUPS-aware print dialogs and therefore listed the remote queues before. Especially printing from the command line would not be covered. The better approach would be modifying the CUPS daemon so that it uses the new library function to find the remote queues and advertize them like its own local queues. Where the CUPS daemon needs to be patched for that we could probably derive from Quantal's CUPS Broadcasting/Browsing forward port patch. The new Bonjour browsing patch being based on the new standard way of Bonjour broadcasting has probably good chances to be accepted upstream. This feature does not only prevent a regression, but it also helps to more easily access printers connected to Mac OS X machines (they broadcasted Bonjour-only all the time) and also for mobile Ubuntu devices. Usually you do not have connected printers to tablets or phones and you carry them around between different local networks, so here it is especially important that they automatically pick up the print queues in the local network. -- Such a patch to the CUPS daemon or an extra daemon to do the browsing and add/remove queues appropriately in the local CUPS environment is also not the best solution but a way to avoid regressions with legacy apps. The real intention from upstream is that all print dialogs browse the print queues available on the local network via Bonjour (under Linux implemented by Avahi), where print queues on the local network are CUPS queues from Linux and Mac OS X but also IPP printers which broadcast themselves via Bonjour (IPP Everywhere printers). Printing on iOS devices (iPhone, iPad, iPod Touch) already works this way. These devices do not allow the setup of local queues at all and they discovcer available print queues via Bonjour. For this the CUPS library has even special functions, see as sample code the program cups/testcups.c to be called as follows: cups/testcups enum 1 "enum" makes it enumerating printers and the number is the number of seconds to Bonjour-browse for network printers. The library function is the function cupsEnumDests() in cups/dest.c. For Bonjour browsing it must be called with a non-zero value for the msec parameter. This feature in the print dialogs is VERY urgent because: - This is how CUPS upstream and also the PWG (Printing Working Group, http://www.pwg.org/) expects how network printing with automatic queue discovery works. - This is less resource-consuming on mobile devices which do not have local print queues. avahi-daemon is running anyway and the CUPS daemon does not need to be running when there are no local queues. - CUPS upstream would not most probably not accept patches on the CUPS daemon to browse for Bonjour-advertized queues and let them appear like local queues. ** Affects: qt Importance: Undecided Status: New ** Affects: qt4-x11 (Ubuntu) Importance: High Status: New ** Changed in: qt4-x11 (Ubuntu) Importance: Undecided => High ** Bug watch added: Email to john@layt #
[Bug 960989] Re: Misplaced spaces on printout on Canon ir 3035
It is really strange, there are several ways to get the broken file. Yesterday I discovered that it happened with "Print to a file (PDF)" in Okular. This is a bug of Okular or the underlying Poppler, but not this bug. When I print into an actual print queue (with ljet4 as driver) Okular sends PostScript (most apps send PDF nowadays) and this PostScript is still correct (therefore this bug is not an Okular bug). CUPS calls the pstopdf filter to turn this PostScript to PDF and this filter uses Ghostscript. On this step the file breaks. You can reproduce it by running the following command with the attached PostScript file: gs -sDEVICE=pdfwrite -sOutputFile=out.pdf printout.ps This means that the bug is actually in Ghostscript, with Ghostscript's "pdfwrite" output device. Moving to Ghostscript ... ** Package changed: okular (Ubuntu) => ghostscript (Ubuntu) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to okular in Ubuntu. https://bugs.launchpad.net/bugs/960989 Title: Misplaced spaces on printout on Canon ir 3035 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ghostscript/+bug/960989/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 960989] Re: Misplaced spaces on printout on Canon ir 3035
It can also be Poppler or any Ubuntu patches on Okular or Poppler. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to okular in Ubuntu. https://bugs.launchpad.net/bugs/960989 Title: Misplaced spaces on printout on Canon ir 3035 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/960989/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 960989] Re: Misplaced spaces on printout on Canon ir 3035
Sorry, have done more checks, it is Okular. If you display the attached file with any PDF reader (Adobe Reader, evince, Okular, Ghostscript, ...) you see that it is broken. Okular has already broken it for you. ** Package changed: ghostscript (Ubuntu) => okular (Ubuntu) -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to okular in Ubuntu. https://bugs.launchpad.net/bugs/960989 Title: Misplaced spaces on printout on Canon ir 3035 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/okular/+bug/960989/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 885324] Re: Completely replace lcms1 by lcms2 in Ubuntu
** Changed in: poppler (Ubuntu) Importance: Undecided => Medium ** Changed in: poppler (Ubuntu) Status: Triaged => In Progress ** Changed in: poppler (Ubuntu) Milestone: None => precise-alpha-2 -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to libkdcraw in Ubuntu. https://bugs.launchpad.net/bugs/885324 Title: Completely replace lcms1 by lcms2 in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/enblend/+bug/885324/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 885324] Re: Completely replace lcms1 by lcms2 in Ubuntu
pitti, they talk about only 5-10 % performance loss in Poppler, but for getting a much less crashing, more reliable, and maintained CM library, I would accept this performance loss. So I think I should add Otani- san's patch for further testing to Precise's package of Poppler. Otani-san, thank you very much for the patch. I will try it out on Ubuntu's Poppler. 5-10 % performance loss is not much for the gain of stability and reliability. It should get applied. Albert, I also highly recommend to apply this patch upstream, as using a more stable, maintained library is much more important then having 5-10 % better performance. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to libkdcraw in Ubuntu. https://bugs.launchpad.net/bugs/885324 Title: Completely replace lcms1 by lcms2 in Ubuntu To manage notifications about this bug go to: https://bugs.launchpad.net/enblend/+bug/885324/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 805303] Re: Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed with the default qt4 gui
I could switch back to the default theme with qtconfig-qt4 and the HPLIP tools keep working. So the problem is actually solved. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to qt4-x11 in Ubuntu. https://bugs.launchpad.net/bugs/805303 Title: Gtk-CRITICAL **: IA__gtk_widget_style_get: assertion `GTK_IS_WIDGET (widget)' failed with the default qt4 gui To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qt4-x11/+bug/805303/+subscriptions -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 513168] Re: Printer options and other strings are not translatable
This is not really a bug, but a missing feature. The feature needs to be added in various packages, first, the PPD files which come from foomatic-db and also from every printer driver package need to get internationalized by making them globalized/multi-language. See http://www.cups.org/documentation.php/doc-1.4/spec-ppd.html, section "Globalized PPD Support". Only the PPDs of the Gutenprint driver and the Postscript printer PPDs of HPLIP are internationalized. Second, the printing dialogs of all applications and printer setup tools like system-config-printer need to support internationalized PPDs. Currently they ignore the translations in the PPDs and simply show the English text. I am adding tasks for printer drivers and packages which contain printing dialogs or printer setup dialogs. If one or another package has already implemented the support for internationalized PPDs, please mark the task as fixed. ** Changed in: foomatic-db (Ubuntu) Status: New => Triaged ** Changed in: gtk+2.0 (Ubuntu) Status: New => Triaged ** Changed in: kdebase (Ubuntu) Status: New => Triaged ** Changed in: system-config-printer (Ubuntu) Status: New => Triaged -- Printer options and other strings are not translatable https://bugs.launchpad.net/bugs/513168 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 513168] Re: Printer options and other strings are not translatable
** Also affects: system-config-printer (Ubuntu) Importance: Undecided Status: New ** Also affects: kdebase (Ubuntu) Importance: Undecided Status: New ** Also affects: gtk+2.0 (Ubuntu) Importance: Undecided Status: New -- Printer options and other strings are not translatable https://bugs.launchpad.net/bugs/513168 You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 234639] Re: usb printer not printing
KDE maintainers, probably you should remove the "Printer Settings" part for Intrepid. -- usb printer not printing https://bugs.launchpad.net/bugs/234639 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 234639] Re: usb printer not printing
At least if you are running KDE 3.x, the "Printer Settings" part in the Control Center is completely out of date. Better do not use it. Do sudo apt-get install system-config-printer hal-cups-utils and use this tool. It will pull in several libraries as it is GTK-based but it will work. ** Changed in: kdebase (Ubuntu) Sourcepackagename: cupsys => kdebase -- usb printer not printing https://bugs.launchpad.net/bugs/234639 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 209220] Re: HP DeskJet 5550 not supported in Hardy
Problem here is that HPLIP has moved PPD generation from Foomatic to the CUPS DDK. The KDE Printing Manager does not support the new PPD generator concept of CUPS 1.2 (PPD generators in /usr/lib/cups/driver/) as it does not ask CUPS for existing PPDs. It looks for physical PPD files and it looks directly into the Foomatic XML database. So it does not find the HPLIP PPDs which are generated by /usr/lib/cups/driver/drv. Solutions are: 1. (Preferred) Make system-config-printer for KDE actually working and configure the desktop that system-config-printer is used by default. 2. Make the KDE Printing Manager dependent on the hpijs-ppds package, so that ready-made PPDs are there (AFAIR we went for this solution also with Gutenprint) I have checked in the GNOME version of system-config-printer and there the DeskJet 5550 is listed. ** Changed in: system-config-printer-kde (Ubuntu) Sourcepackagename: hplip => system-config-printer-kde Importance: Undecided => High Assignee: (unassigned) => Jonathan Riddell (jr) Target: None => ubuntu-8.04 ** Also affects: kdebase (Ubuntu) Importance: Undecided Status: New ** Changed in: kdebase (Ubuntu) Importance: Undecided => High Assignee: (unassigned) => Jonathan Riddell (jr) Target: None => ubuntu-8.04 -- HP DeskJet 5550 not supported in Hardy https://bugs.launchpad.net/bugs/209220 You received this bug notification because you are a member of Kubuntu Team, which is subscribed to kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 149899] Re: foomatic-db-gutenprint NEEDs ijsgutenprint
gutenprint (5.0.1-0ubuntu8) gutsy; urgency=low * debian/control, debian/control.in: Re-introduced foomatic-db-gutenprint's dependency on ijsgutenprint, foomatic-db-gutenprint NEEDs ijsgutenprint (LP: #149899). Added also dependencies on foomatic-db-engine (needed to generate the PPDs) and foomatic-filter (needed to print with the PPDs). Also updated Ghostscript dependency in ijsgutenprint to the current situation. * debian/rules: Do not include obsolete link /usr/share/cups/model/gutenprint which is deleted by the post-install script anyway (LP: #149729). -- Till Kamppeter <[EMAIL PROTECTED]> Sat, 6 Oct 2007 17:47:33 +0100 ** Changed in: gutenprint (Ubuntu) Status: Fix Committed => Fix Released -- foomatic-db-gutenprint NEEDs ijsgutenprint https://bugs.launchpad.net/bugs/149899 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 99372] Re: MASTER: [Feisty] KDE Printing Manager does not list the PPDs of Gutenprint
Cimmo, for Gutenprint it is really different. The cupsys-driver- gutenprint package does not ship any PPDs but a much smaller PPD generator. This generator is invoked by CUPS if a client asks CUPS for PPD listings or PPDs. The KDE Printing Manager does not ask CUPS for PPDs. It searches by itself in the file system and also browses Foomatic XML files. So it does not find PPDs for cupsys-driver-gutenprint. Therefore the suggestion by Jonathan and me to replace cupsys-driver- gutenprint by foomatic-db-gutenprint and ijsgutenprint. The change of the optimization level can be done independently to fix the other, independent PPD listing problem. -- MASTER: [Feisty] KDE Printing Manager does not list the PPDs of Gutenprint https://bugs.launchpad.net/bugs/99372 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kdebase in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 149899] Re: foomatic-db-gutenprint NEEDs ijsgutenprint
** Summary changed: - foomati-db-gutenprint NEEDs ijsgutenprint + foomatic-db-gutenprint NEEDs ijsgutenprint ** Changed in: gutenprint (Ubuntu) Status: Confirmed => Fix Committed -- foomatic-db-gutenprint NEEDs ijsgutenprint https://bugs.launchpad.net/bugs/149899 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 149899] foomati-db-gutenprint NEEDs ijsgutenprint
Public bug reported: To fix bug 99372 Jonathan Riddell has decided on using foomatic-db- gutenprint to provide the Gutenprint PPDs as the KDE Printing Manager cannot cope with the on-the-fly PPD generator of cupsys-driver- gutenprint. To save space in Kubuntu he has released the "Depends" on ijsgutenprint. foomatic-db-gutenprint contains Foomatic XML data to generate PPD files for the IJS driver of Gutenprint, ijsgutenprint. These PPDs are not able to use the cupsys-driver-gutenprint driver. Not having ijsgutenprint installed makes the PPDs generated from the data in foomatic-db- gutenprint non-functional. So the "Depends" on ijsgutenprint cannot be removed to save space on Kubuntu. The correct solution is to take cupsys-driver-gutenprint out of the Kubuntu seed and add ijsgutenprint instead. ** Affects: gutenprint (Ubuntu) Importance: Critical Status: Confirmed ** Affects: kubuntu-meta (Ubuntu) Importance: Critical Assignee: Jonathan Riddell (jr) Status: Confirmed ** Changed in: gutenprint (Ubuntu) Importance: Undecided => Critical Status: New => Confirmed Target: None => ubuntu-7.10-rc ** Also affects: kubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Changed in: kubuntu-meta (Ubuntu) Importance: Undecided => Critical Target: None => ubuntu-7.10-rc ** Changed in: kubuntu-meta (Ubuntu) Status: New => Confirmed ** Changed in: kubuntu-meta (Ubuntu) Assignee: (unassigned) => Jonathan Riddell (jr) -- foomati-db-gutenprint NEEDs ijsgutenprint https://bugs.launchpad.net/bugs/149899 You received this bug notification because you are a member of Kubuntu Team, which is a bug contact for kubuntu-meta in ubuntu. -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 29622] Re: Firefox does not print the headers and footers.
This is a problem of the browsers, as they can find out about the unprintable margins of the printer by means of the CUPS API. The CUPS API gives access to the complete content of the PPD file and the PPD contains the margin info. So this bug has to be assigned to both the printing part of the Gecko engine and the printing part of Konqueror. The bug is not in CUPS, CUPS has everything to tell the apps how big the unprintable margins of each configured printer are. ** Changed in: cupsys (Ubuntu) Sourcepackagename: cupsys => firefox ** Changed in: firefox (Ubuntu) Status: Needs Info => Confirmed ** Also affects: kdebase (Ubuntu) Importance: Undecided Status: Unconfirmed ** Changed in: kdebase (Ubuntu) Importance: Undecided => Medium Status: Unconfirmed => Confirmed ** Summary changed: - Firefox does not print the headers and footers. + Many web browsers not print the headers and footers. -- Many web browsers not print the headers and footers. https://launchpad.net/bugs/29622 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 23099] Re: ghostscript needs patch for KRGB printing
Does this problem still occur with current Edgy (try with a live CD if you do not want to install)? ** Changed in: hplip (Ubuntu) Status: Unconfirmed => Needs Info -- ghostscript needs patch for KRGB printing https://launchpad.net/bugs/23099 -- kubuntu-bugs mailing list kubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
