Victor thank you very much for your great verification reports on Xenial
and Bionic. I have marked these two as verified now.
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
** Tags removed: verification-done-bionic verification-needed-xenial
** Tags added:
yparitcher, simply report a new bug describing the regression and in
which Ubuntu/ModemManager versions you have found it. We will add the
rest to make an SRU bug report out of it. Post a link to your bug report
here. Thanks.
--
You received this bug notification because you are a member of
debdiff for the full SRU for Bionic: Upgrade to 1.10 plus regression
fix.
** Patch added: "modemmanager_1.6.8-2ubuntu1_1.10.0-1~ubuntu18.04.2.debdiff"
debdiff to update the Bionic SRU to fix the regression.
** Patch added:
"modemmanager_1.10.0-1~ubuntu18.04.1_1.10.0-1~ubuntu18.04.2.debdiff"
debdiff to fix the regression in eoan.
** Patch added: "modemmanager_1.10.0-1_1.10.0-1ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/disco/+source/modemmanager/+bug/1819615/+attachment/5261891/+files/modemmanager_1.10.0-1_1.10.0-1ubuntu1.debdiff
--
You received this bug notification
** Also affects: modemmanager (Ubuntu Eoan)
Importance: High
Status: Fix Released
** Also affects: libqmi (Ubuntu Eoan)
Importance: High
Status: Fix Released
** Also affects: libmbim (Ubuntu Eoan)
Importance: High
Status: Fix Released
** Also affects: modemmanager
yparitcher, thank you very much for your fix. We will add it to the SRU of the
modemmanager package and also apply it to eoan. Please watch out this bug
report for a new verification call.
To the SRU team: The regression of the modemmanager SRU is fixed and I will
soon put up a new debdiff for
** Changed in: modemmanager (Ubuntu Bionic)
Status: Confirmed => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819615
Title:
For additional hardware support, modemmanager needs to
Probably bug 1826403 is related. It got reported upstream as
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/166
Please check whether your bug is perhaps the same and comment on/follow
the upstream bug.
** Bug watch added:
yparitcher, thank you for the upstream bug report. As soon as upstream
finds a (backportable) solution we will add it to this SRU and report
back here.
** Changed in: modemmanager (Ubuntu Bionic)
Status: Fix Committed => Confirmed
--
You received this bug notification because you are a
yparitcher, as this SRU consists of three packages, ModemManager itself
and the two libraries, try at first to downgrade only modemmanager to
the original. If this solves the problem, it is caused by modemmanager,
if not, downgrade one of the libraries, then try to downgrade the other,
... until
Brian, do you have some link (bug report, ...) to this failure?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819615
Title:
For additional hardware support, modemmanager needs to be upgraded to
** Tags removed: verification-needed
** Tags added: verification-done
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1819615
Title:
For additional hardware support, modemmanager needs to be upgraded
Can you please attach your /etc/cups/cupsd.conf, /etc/cups/cups-
files.conf, and /etc/cups/printers.conf files.
Please also attach your *.ppd files in /etc/cups/ppd/.
Also follow the instructions of the section "CUPS error_log" on
https://wiki.ubuntu.com/DebuggingPrintingProblems and then run
#
Could you please try the following:
In a terminal window run the command
sudo systemctl stop cups-browsed
This turns off cups-browsed completely.
Does the problem go away by this?
** Changed in: cups-filters (Ubuntu)
Status: Confirmed => Incomplete
--
You received this bug
According to the attached log files hp-setup has created a print queue
with the same name as a queue created by cups-browsed, overwriting this
queue. As cups-browsed removes all the queues it created when it shuts
down, it also has removed this queue.
Normally cups-browsed gets a notification
** Changed in: cups-filters (Ubuntu)
Status: Confirmed => In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1731417
Title:
Installed network printer removed automatically when turned
** Changed in: libqmi (Ubuntu Bionic)
Assignee: (unassigned) => Till Kamppeter (till-kamppeter)
** Changed in: libmbim (Ubuntu Bionic)
Assignee: (unassigned) => Till Kamppeter (till-kamppeter)
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Upstream cannot reproduce, OP does not have the hardware any more,
closing ...
** Changed in: cups (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Here is an updated debdiff for gtk+3.0 in Ubuntu Disco. It is based on
the current gtk_3.0 package of Disco with the patch of
https://gitlab.gnome.org/GNOME/gtk/merge_requests/717
applied, this patch exactly:
The patch got also merged into the 3.24 branch of GTK:
https://gitlab.gnome.org/GNOME/gtk/merge_requests/717
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763520
Title:
after upgrade to bionic,
The patch got merged upstream.
See
https://gitlab.gnome.org/GNOME/gtk/merge_requests/434
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763520
Title:
after upgrade to bionic, printing fails
hailfinger, this would mean that Brother's PostScript printers only work
with PostScript level 2 instead of level 3, this is at least what cups-
filters will do different after your change.
I have modified cups-filters (the pdftops filter) now to emit PostScript
level 2 on Brother printers,
As soon as the patch is incorporated upstream I will post the resulting
patch here.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763520
Title:
after upgrade to bionic, printing fails without
Updated the proposed patch for upstream according to their requirements.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1763520
Title:
after upgrade to bionic, printing fails without explanation /
Thanks. Closed network-manager tasks.
** Changed in: network-manager (Ubuntu Bionic)
Status: New => Invalid
** Changed in: network-manager (Ubuntu Cosmic)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Does this need any fix in network-manager? Seems to be fully fixed by
the kernel patch.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1818204
Title:
Qualcomm Atheros QCA9377 wireless does not work
Thanks, nice collection of crashes, but no NetworkManager.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1810316
Title:
gnome-control-center SIGABRT when n-m is not working (G_IS_OBJECT
(object))
To anyone who has observed this problem:
Please check the contents of your /var/crash/ directory.
Is there a file with the ".crash" extension and NetworkManager or
networkmanager in its name and the day when you observed the problem as
file date?
In this case also NetworkManager has crashed.
The SRU bug 1809132 has the same proposed package as this one and it got
marked verified after three months without complaints and also after
some testing by me and in agreement with Ken VanDine, Will Cooke,
Olivier Tilloy.
So at least the new network-manager version should not cause any
By the way, if there is one SRU package to fix several separately
reported bugs, each of these bugs should link to the others, so that a
single bug cannot cause the removal of the SRU even if it gets verified
in the other bugs. Or the SRU package needs one "master bug" where the
verification gets
This temporary queue (Kyocera_ECOSYS_P6026cdn) is actually not needed
here. Therefore I have reported this upstream issue on CUPS:
https://github.com/apple/cups/issues/5546
But anyhow, the GUIs need to correctly support temporary print queues of
CUPS.
** Bug watch added:
Fixed modemmanager package.
** Patch added: "modemmanager_1.6.8-2ubuntu1_1.10.0-1~ubuntu18.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615/+attachment/5247989/+files/modemmanager_1.6.8-2ubuntu1_1.10.0-1~ubuntu18.04.1.debdiff
--
You received this bug
Edelharn, the update is not ready yet. Please keep watching bug 1819615
(subscribe to it) and when it is told there that the new package
(modemmanager 1.10) is ready for testing, you can install it. And give
your feedback also in that bug so that we can pass the new package into
the official
Fixed libmbim package.
** Patch added: "libmbim_1.14.2-2.1ubuntu1_1.18.0-1~ubuntu18.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615/+attachment/5247983/+files/libmbim_1.14.2-2.1ubuntu1_1.18.0-1~ubuntu18.04.1.debdiff
--
You received this bug notification
Fixed libqmi package.
** Patch added: "libqmi_1.18.0-3ubuntu1_1.22.0-1.2~ubuntu18.04.1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/modemmanager/+bug/1819615/+attachment/5247982/+files/libqmi_1.18.0-3ubuntu1_1.22.0-1.2~ubuntu18.04.1.debdiff
--
You received this bug notification
This is most probably covered by the update to modemmanager 1.10, bug
1819615.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1821052
Title:
No connexion with mobile broadband
To manage
Yuan-Chen, Alex: I have finished to prepare the three needed packages,
including a fix on libqmi coming in yesterday. Now I am simply waiting
for the upload of the packages getting sponsored (probably by Ken
VanDine) and the SRU team putting the packages into bionic-proposed.
Feel free to add
I think the problem here is CUPS' own method of generating temporary
queues for discovered driverless printers. gnome-control-center, and
probably other GUIs, like the GTK print dialog, cannot cope with this.
So we leave this bug report assigned to gnome-control-center for now.
Christian, if you
Christian, both your attached PPD files are auto-generated, and both
pass cupstestppd.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1813825
Title:
"driverless" printer workflow has bad usability/
Christian, first, it seems that you did "cupstestppd" on a PPD file
which is not auto-generated:
--
$ sudo cupstestppd /etc/cups/ppd/Kyocera-ECOSYS-P6026cdn.ppd
/etc/cups/ppd/Kyocera-ECOSYS-P6026cdn.ppd: FAIL
**FAIL** Missing choice *Option18 SDCard in UIConstraints "*KCCollate
Which browser did you use?
Does the preview of the browser's print dialog also show the broken printout?
Can you print the same web pages with another browser?
** Changed in: cups (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Replacement for the debdiff for libqmi 1.22.0 in Bionic.
This debdiff also contains the most recent fixes In Debian and in Disco
(see https://bugs.launchpad.net/ubuntu/+source/libqmi/1.22.0-1.2):
--
libqmi (1.22.0-1.2) unstable; urgency=medium
* Non-maintainer upload.
* Add
** Description changed:
[Impact]
- * The new modemmanager package adds DW5820e support.
- * This modemmanager version is needed to support new devices.
+ * The new modemmanager package adds DW5820e support.
+ * This modemmanager version is needed to support new devices.
[Test Case]
** Description changed:
+ [Impact]
+
+ * The new modemmanager package adds DW5820e support.
+ * This modemmanager version is needed to support new devices.
+
+ [Test Case]
+
+ * install modemmanager, libmbim, and libqmi from -proposed
+ * reboot and try WWAN function to see if any
Now after 3 months time for testing and no complaints coming up, Ken
VanDine, Will Cooke, Olivier Tilloy, and me agreed on considering this
SRU as verified. So I have marked this bug report appropriately.
Thanks to everyone who has tested this.
** Tags removed: verification-needed
Ian, could you perhaps apply the patch of comment #13 and see whether
you get your problem fully solved (no need of setting AuthType Default
for /)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Also on the Bionic VM on my main laptop I have updated network-manager
to 1.10.14 and there are no issues.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809132
Title:
Updated bionic to the current
Now my Bionic test box is running for the whole weekend and it does not
show any irregularities. No crash reports. The new network-manager seems
to work fine on Bionic.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Sorry, I mean network-manager 1.10.14.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1809132
Title:
Updated bionic to the current 1.10 stable version
To manage notifications about this bug go to:
I have set up Bionic on an old laptop now and updated it with -proposed
included, landing on network-manager 1.10.
I have done some tests:
- Connection via Wi-Fi works (also switching to a second WLAN and when the
second WLAN goes away it automatically returns to the first),
- Connection with a
debdiff for libqmi 1.22.0 in Bionic. The upstream source tarball is the
same as for Disco.
** Patch added: "libqmi_1.18.0-3ubuntu1_1.22.0-0ubuntu1.debdiff"
https://bugs.launchpad.net/ubuntu/+source/libqmi/+bug/1819615/+attachment/5245702/+files/libqmi_1.18.0-3ubuntu1_1.22.0-0ubuntu1.debdiff
debdiff for modemmanager 1.10 in Bionic. The upstream source tarball is
the same as for Disco.
** Patch added: "modemmanager_1.6.8-2ubuntu1_1.10.0-0ubuntu1.debdiff"
debdiff for libmbim 1.18.0 in Bionic. The upstream source tarball is the
same as for Disco.
** Patch added: "libmbim_1.14.2-2.1ubuntu1_1.18.0-0ubuntu1.debdiff"
I have made Bionic packages for ModemManager 1.10 and the needed
libraries now. I have attached the debdiffs and the upstream tarballs
are the same as of the Disco packages.
Ken, could you upload these packages for me.
Alex, if we need to go through the SRU process (is this needed for
hardware
** Changed in: libmbim (Ubuntu Bionic)
Status: New => In Progress
** Changed in: libqmi (Ubuntu Bionic)
Status: New => In Progress
** Changed in: modemmanager (Ubuntu Bionic)
Status: New => In Progress
--
You received this bug notification because you are a member of
Added tasks for libmbim and libqmi as their current versions are needed
by ModemManeger 1.10.
** Also affects: libmbim (Ubuntu)
Importance: Undecided
Status: New
** Changed in: libmbim (Ubuntu)
Importance: Undecided => High
** Also affects: libqmi (Ubuntu)
Importance: Undecided
Public bug reported:
To have Bionic, the current LTS, working with as wide of a range of
modems as possible we need to have it upgraded to the current 1.10
versions. Also the underlying libraries need to get upgraded
appropriately.
** Affects: modemmanager (Ubuntu)
Importance: High
Esko, thanks for the feedback. I have marked the fix as verified now so
it will get an official update for Bionic soon.
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Till Kamppeter (till-kamppeter)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817947
Title:
On Cosmic, there is no automa
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Till Kamppeter (till-kamppeter)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815742
Title:
latest network-manager segfau
** Changed in: network-manager (Ubuntu Bionic)
Assignee: (unassigned) => Till Kamppeter (till-kamppeter)
** Changed in: network-manager (Ubuntu)
Assignee: (unassigned) => Till Kamppeter (till-kamppeter)
--
You received this bug notification because you are a member of Ubunt
Should we perhaps make the GNOME network setup tool depend on
network-manager-openvpn-gnome
network-manager-vpnc-gnome
network-manager-pptp-gnome
This should at least solve this problems for some when updating.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
Sebastien Bacher (seb128) has already informed upstream on
https://gitlab.freedesktop.org/NetworkManager/NetworkManager/issues/124#note_126100
and following comments.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
We were not aware of this, most probably because in most cases it does
not influence the result, a correct printout.
Most probably this is actually a Ghostscript bug so I recommend to
report it to Ghostscript upstream, https://bugs.ghostscript.com/. Please
include your Ghostscript command line
Seb, I think what he means is not aoto-fill of the login credentials,
but rather how cookies are handled.
On modern web sites it is standard now to ask the user before starting
to use Cookies. Usually there a[ppears a question on the site the first
time you visit it (the question is provided by
Thanks Esko for your investigations. I have uploaded and appropriately
patched CUPS package for Bionic now. As soon as it gets approved you
will be asked for testing here. Please do the testing then and give us
feedback whether it solves your problem, so that we can make the fix an
official update
debdiff of the fix.
** Patch added: "cups_2.2.7-1ubuntu2.3_2.2.7-1ubuntu2.4.debdiff"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1783298/+attachment/5243039/+files/cups_2.2.7-1ubuntu2.3_2.2.7-1ubuntu2.4.debdiff
--
You received this bug notification because you are a member of Ubuntu
** Summary changed:
- AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
+ [SRU] AuthInfoRequired negotiate in cups 2.2.7 in Bionic does not work
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Reported upstream as https://github.com/apple/cups/issues/5536.
** Bug watch added: github.com/apple/cups/issues #5536
https://github.com/apple/cups/issues/5536
** Also affects: cups via
https://github.com/apple/cups/issues/5536
Importance: Unknown
Status: Unknown
--
You
** Description changed:
network-manager has a facility to automatically pop up a Captive Portal
of a Wi-Fi network if required for access to the internet through that
network. It does test accesses and on failure it triggers the pop-up.
Unfortunately, this does not work in Cosmic due
Public bug reported:
network-manager has a facility to automatically pop up a Captive Portal
of a Wi-Fi network if required for access to the internet through that
network. It does test accesses and on failure it triggers the pop-up.
Unfortunately, this does not work in Cosmic due to an upstream
Marc, I am on Disco and after a system update today I have the following
Ghostscript:
--
ghostscript (9.26~dfsg+0-0ubuntu5) disco; urgency=medium
* SECURITY REGRESSION: High RIP_MAX_CACHE makes cups output device fail
(LP: #1815339)
- debian/patches/lp1815339.patch: fix logic
The fix for this bug got reverted as it caused a regression, bug
1817308. Therefore I am re-opening this bug.
A solution for this regression got already committed by the upstream
developers of Ghostscript, see the upstream bug report:
http://bugs.ghostscript.com/show_bug.cgi?id=700584
**
To the security team:
The Ghostscript developers have fixed the problem now. See
http://bugs.ghostscript.com/show_bug.cgi?id=700584
Can another update be issued with this fix?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
*** This bug is a duplicate of bug 1817308 ***
https://bugs.launchpad.net/bugs/1817308
** This bug has been marked a duplicate of bug 1817308
GhostScript Update causes Blue Background
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
The Ubuntu security team has applied the fix for this bug to the
GhostScript 9.26 which they have issued as security update to several
Ubuntu versions.
Unfortunately, this fix has caused a regression. It was reported here:
https://bugs.launchpad.net/bugs/1817308
The user tells that all pages
The bug is most probably caused by a regression fix on Ghostscript 9.26,
issued by the security team.
Please provide us the error_log (in debug mode, see
https://wiki.ubuntu.com/DebuggingPrintingProblems#CUPS_error_log) of one
of your failing (comin out in blue) print jobs.
I also reported this
The problem is most probably caused bei the Ghostscript which does the
conversion to the printer's PCL format not being able to cope with the
PDF after the form got flattened. Old cups-filters versions (< 1.22.x)
use pdftocairo or Ghostscript for form-flattening, newer cups-filters
use QPDF and
Which version of cups-filters are you using?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817033
Title:
Unable to correctly print PDF file: Error: Ignoring spurious ET
operator.
To manage
Can you update your Debian unstable so that you get cups-filters 1.22.x?
Does this solve your problem?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817033
Title:
Unable to correctly print PDF
The PDF file contains a fillable form. Did you fill it in and save the
PDF with filled form before printing? Or did you print the original PDF
without filling the form?
** Changed in: cups-filters (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a
** Package changed: cups (Ubuntu) => cups-filters (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1817033
Title:
Unable to correctly print PDF file: Error: Ignoring spurious ET
operator.
Michael Sweet was not able to reproduce this bug with the Canon printer
he got at Apple. See
https://github.com/apple/cups/issues/5512
Please post in this bug report to directly interact with Michael.
Before doing so, get a setup of Disco (upcoming Ubuntu 19.04) and check
whether your problem
Christian, where is the rest which you wanted to post the day after Jan
30?
** Changed in: gnome-control-center (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
If you need the jobs coming out in the correct order, have only one
queue and print the jobs through this one queue.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1816529
Title:
The print order
This is not a bug.
CUPS prints jobs only in the order of sending if they are printed via
the same print queue. If you create two different queues for the same
physical printer and print one job into each of them CUPS will process
them in parallel and so the order in which the jobs get printed is
@fargoth, sorry for that comment. I was wrong. What got actually fixed
was another thing which I observed during the investigations for this
bug.
Therefore I have re-opened
https://github.com/OpenPrinting/cups-filters/issues/22
Please see my comments #5 and #6.
--
You received this bug
*** This bug is a duplicate of bug 1815307 ***
https://bugs.launchpad.net/bugs/1815307
** This bug has been marked a duplicate of bug 1815307
ipp printer isn't shown automatically - adding it errors with a CUPS
internal error
--
You received this bug notification because you are a
A similar report got also to CUPS upstream:
https://github.com/apple/cups/issues/5512
and it seems that there is either a firmware bug in the AirPrint-
supporting Canon printers or some problem with the client-side IPP
implementation (which is in libcups, part of CUPS).
Michael Sweet, author of
I have added this case to upstream discussion now:
https://github.com/OpenPrinting/cups-filters/issues/65
** Bug watch added: github.com/OpenPrinting/cups-filters/issues #65
https://github.com/OpenPrinting/cups-filters/issues/65
--
You received this bug notification because you are a member
The best solution here is a proper fix by Ghostscript's upstream
developers. For the case that this fix will not appear soon, the
workaround would be to patch CUPS to supply RIP_MAX_CACHE=0 instead of
RIP_MAX_CACHE=128m, so that Ghostscript decides on cache sizes by
itself.
--
You received this
The issues referenced in the previous comment are all fixed upstream
now. If they were the cause for your problem, your problem will be
solved in Disco.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Probably your printer suffers the problem shown in the following
upstream bug report on cups-filters:
https://github.com/OpenPrinting/cups-filters/issues/22
It is currently worked on this, especially also here
https://github.com/OpenPrinting/cups-filters/pull/86
and here
Reported to Ghostscript upstream as
https://bugs.ghostscript.com/show_bug.cgi?id=700584
** Bug watch added: Ghostscript (AFPL) Bugzilla #700584
http://bugs.ghostscript.com/show_bug.cgi?id=700584
** Also affects: gs-gpl via
http://bugs.ghostscript.com/show_bug.cgi?id=700584
Importance:
Here is a reproducer (with GS 9.26) consisting in a pure Ghostscript
command line:
cat appout.pdf | RIP_MAX_CACHE=128m gs -dQUIET -dPARANOIDSAFER -dNOPAUSE
-dBATCH -dNOINTERPOLATE -dNOMEDIAATTRS -dShowAcroForm -sstdout='%stderr'
-sOutputFile='%stdout' -sDEVICE=cups -sMediaClass=Cassette
Thanks for the PPD file (and the job captured from the app). Now I can
reproduce the crash with
cupsfilter -p MG5400LAN-Gutenprint.ppd -o PageSize=w288h432 -m
application/vnd.cups-raster appout.pdf > out.prn
out.prn is empty. Nothing has been written to it when the crash
happened.
--
You
Fedik, can you please attach the PPD file of your print queue (from the
/etc/cups/ppd/) directory? Thanks.
** Changed in: ghostscript (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Attached is the debdiff with the proposed fix of comment #19 applied.
Someone with appropriate upload rights to Disco, please upload it.
I could not actually test it as I have no access to a Microsoft VPN,
I do not see any regression though. I can access Canonical's VPNs and
while having
In comment #13 you told that it prints with Ghostscript via
lp -d duplex -o fit-to-page -o pdftops-renderer=gs
Did it again send the job with a weird paper size? Or did the job come
out straight away?
The "-o fit-to-page" should scale each page into the standard page size.
Does
lp -d duplex
501 - 600 of 14285 matches
Mail list logo
