Upstream bug
https://github.com/OpenPrinting/cups/issues/1118
is fixed now.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089231
Title:
CUPS passes illegal characters from PPD file to printer IPP
This needs merging, especially for the firmware file location as of my
change from 10 Apr 2024, Sync is only possible if Debian has changed the
firmware file location, too. Also waht I mentioned on my last merge on
06 Sep 2021 should stay conserved.
Ideal would be just back-syncing these changes i
** Changed in: cups (Ubuntu)
Status: New => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1053196
Title:
Printer EPSON LX-810L with ADAPTER CENTRONICS-TO-USB Cable prints VERY
BAD
The fixed CUPS Snap (2.4.12-1) has landed in the Snap Store now:
https://snapcraft.io/cups
For those who have the CUPS Snap currently installed, it will get auto-
updated. Check with
snap list cups
whether the version is already 2.4.12-1. In this case the auto-update
has happened.
Try
Note: This bug report is about the CUPS Snap, not the Ubuntu package of
CUPS in DEB format, for what the "cups (Ubuntu)" task is for.
Bugs on the CUPS Snap, please only report upstream:
https://github.com/OpenPrinting/cups-snap/issues
This bug is now fixed with the following upstream commit:
*** This bug is a duplicate of bug 2021956 ***
https://bugs.launchpad.net/bugs/2021956
** This bug has been marked a duplicate of bug 2021956
crash cups-proxyd
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
Attached is the debdiff with the fix for this bug (updating to upstream
version 6.2.7).
Unfortunately the "brlaser" source package is not in my PPU package
list. Can therefore somebody with appropriate rights sponsor this
upload, so that it makes it into Plucky?
The changes on the code are very s
** Description changed:
[Availability]
- The package pdfio is already in Ubuntu universe.
- The package pdfio build for the architectures it is designed to work on.
- It currently builds and works for architectures: amd64, arm64, armhf,
ppc64el, riscv64, s390x
- Link to package https://
** Description changed:
[Availability]
- The package pdfio is already in Ubuntu universe.
- The package pdfio build for the architectures it is designed to work on.
- It currently builds and works for architectures: amd64, arm64, armhf,
ppc64el, riscv64, s390x
- Link to package https://
** Description changed:
[Availability]
- The package pdfio is already in Ubuntu universe.
- The package pdfio build for the architectures it is designed to work on.
- It currently builds and works for architectures: amd64, arm64, armhf,
ppc64el, riscv64, s390x
- Link to package https://
** Description changed:
[Availability]
- The package pdfio is already in Ubuntu universe.
- The package pdfio build for the architectures it is designed to work on.
- It currently builds and works for architectures: amd64, arm64, armhf,
ppc64el, riscv64, s390x
- Link to package https://
** Description changed:
[Availability]
- The package pdfio is already in Ubuntu universe.
- The package pdfio build for the architectures it is designed to work on.
- It currently builds and works for architectures: amd64, arm64, armhf,
ppc64el, riscv64, s390x
- Link to package https://
** Description changed:
[Availability]
- The package pdfio is already in Ubuntu universe.
- The package pdfio build for the architectures it is designed to work on.
- It currently builds and works for architectures: amd64, arm64, armhf,
ppc64el, riscv64, s390x
- Link to package https://
** Description changed:
[Availability]
- The package pdfio is already in Ubuntu universe.
- The package pdfio build for the architectures it is designed to work on.
- It currently builds and works for architectures: amd64, arm64, armhf,
ppc64el, riscv64, s390x
- Link to package https://
** Description changed:
[Availability]
- TODO: The package TBDSRC is already in Ubuntu universe.
- TODO: The package TBDSRC build for the architectures it is designed to work
on.
- TODO: It currently builds and works for architectures: TBD
- TODO: Link to package https://launchpad.net/ubuntu/+s
Public bug reported:
[Availability]
TODO: The package TBDSRC is already in Ubuntu universe.
TODO: The package TBDSRC build for the architectures it is designed to work on.
TODO: It currently builds and works for architectures: TBD
TODO: Link to package https://launchpad.net/ubuntu/+source/TBDSRC
Tried it out right now by manually downloading the binary package from
Launchpad and it works!! Thanks a lot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2102002
Title:
Icons in launcher do not sc
Could you do the following:
sudo dpkg -P --force-depends cups-daemon
sudo apt install cups-daemon
sudo systemctl start cups
cupsctl --debug-logging
lpstat -r
lpstat -v
lpstat -l -e
driverless
and post the output of the commands here. Continue until you have done
al
Another possibility would be making int configurable in the "Ubuntu
Desktop" section of G-C-C:
Scroll wheel over dock: (*) Scroll icons
( ) Switch workspace
( ) Scroll when overfull, otherwise switch workspace
--
You received this bug n
And in my opinion this should be scrolling the icons so that one can
handle an overfull dock. The only way to scroll the icons without scroll
wheel is to move the pointer into a very small area at the upper or
lower end of the dock and wait for the then slowly scrolling icons. This
is really awkwar
OK, the Snaps need the CUPS Snap to actually be able to print, so you
need to re-install it:
sudo snap install cups
I asked you to remove it to have better control on the recovery of the
system's CUPS, but now as we have re-established its original
configuration you can re-install the Snap.
Could you run
ls -la /usr/lib/systemd/system/ | grep /dev/null
ls -la /etc/systemd/system/ | grep /dev/null
ls -la /var/run/systemd/system/ | grep /dev/null
and post the output here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Could you do:
sudo rm /etc/systemd/system/cups-browsed.service
sudo rm /etc/systemd/system/cups.socket
sudo systemctl start cups
cupsctl --debug-logging
lpstat -r
lpstat -v
lpstat -l -e
and post the output?
--
You received this bug notification because you are a mem
Could you again run the commands of comment #31?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083530
Title:
gnome-control-center not able to add printer or make settings
To manage notifications a
Could you run
file /lib/systemd/system/cups.service
file /usr/lib/systemd/system/cups.service
and post the output here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083530
Title:
gnome-c
Public bug reported:
I have the usual Ubuntu with GNOME and with the dock on the left edge of
the screen. Distro version is Plucky.
My display has 4K resolution, 3840x2160, and "Scale:" is set to 200 %,
no fractional scaling. The dock icon size set in the G-C-C is 48 pixels.
I have many icons (>
And now please do the commands of comment #31.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083530
Title:
gnome-control-center not able to add printer or make settings
To manage notifications abo
Now we have cleaned up the mess of your use of "systemctl mask ..." and
of your attempt to replace your system's CUPS by the Snap of CUPS.
Next step is to investigate to find out what the actual bug is.
In the print dialog of your evince there are two entries. The second
entry, "BROTHER_MFC_L2710
Do you have another machine (Linux or Mac) in your network which is
sharing the printer "Brother-Printer"?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083530
Title:
gnome-control-center not able
Could you copy your files /etc/cups/printers.conf and
/etc/cups/ppd/Brother-Printer.ppd and attach them to this bug report?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083530
Title:
gnome-control
It seems that CUPS is still masked and it seems that by force-removing
and re-installing it one does not get it unmasked.
Did you execute the commands as I told you in comment #23?
Note that I have derived this command sequence from:
https://askubuntu.com/questions/804946/systemctl-how-to-un
Sorry, I meant that you wanted to remove the CUPS Debian packages after
you have hit the bug. I have then guided you to get all back to its
original state, as replacing the original CUPS by the CUPS Snap could
perhaps work around the problem but does not allow us to investigate it.
And as for most
Warning added to cups-snap repo ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083530
Title:
gnome-control-center not able to add printer or make settings
To manage notifications about this bug
Seb, you see here why the future lies in immutable distros, it is so
easy to create a complete mess with conventional ones ...
The steps were all an act of desperation. By stumbling over the cups-
snap repo on OpenPrinting (and therefore installing the CUPS Snap) Marc
has tried to get rid of the D
So first, please try to do as described in the question I linked (this
is the text from there but "translated" to CUPS):
-
First check that the unit file is a symlink to /dev/null
file /lib/systemd/system/cups.service
it should return:
/lib/systemd/system/cups.service: symbolic link
For you the snapped CUPS daemon is running, not the one of the Debian
package. This means that principally you can print, especially as your
printer is driverless. Printer setup tools like system-config-printer
and KDE Print Manager can communicate with the CUPS daemon normally. You
only would see
`systemctl unmask ...` actually does not work. See this question on Ask
Ubuntu and the selected answer (green check mark) for it
https://askubuntu.com/questions/804946/systemctl-how-to-unmask
Seems to by a systemd bug.
But note that this is not your original GNOME problem. That problem
alread
For me it all seems like GNOME (and its underlying GUI library GTK) is
not able to fully access the printing system, but other applications,
desktops, and GUI libraries are able to fully access.
Could you set CUPS to debug logging:
cupsctl --debug-logging
and do 2 tests:
1. Open the print d
Could you run the command
ps aux | grep cups
and post the output here?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083530
Title:
gnome-control-center not able to add printer or make setting
Also, are you in the "lpadmin" group? Check the /etc/group file.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083530
Title:
gnome-control-center not able to add printer or make settings
To manage
Can you post a screenshot of the main view of the print dialog of
evince, where one sees the list of available printers (not the print
preview)?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2083530
T
The link to your evince screenshot does not work.
You can generally attach image files directly to Launchpad bug comments,
you do not need to use any third-party service to host images or other
files. Especially then the images keep conserved for the future as on
Launchpad there is no space limit,
First, at least before your switched to the Snap package of CUPS, you
were able to use KDE Print Manager and system-config-printer to manager
your printer, create queues, set option defaults, ...?
And were you able to print from any application, including GNOME
applications like evince?
Where you
@michaelweghorn thanks a lot for the merge request.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100307
Title:
gtk4 fails to build with cpdb-libs 2.0~b7
To manage notifications about this bug go
Why are there tasks on fragments and warp? Do they also use cpdb-libs?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2100307
Title:
gtk4 fails to build with cpdb-libs 2.0~b7
To manage notifications
While chatting about this on our CPDB Telegram channel, Michael Weghorn
from LibreOffice did a quick fix for the GTK print dialog:
https://gitlab.gnome.org/michaelweghorn/gtk/-/commit/40c3da77013284ca3f65c17302c2db3b20081c47
I asked him to post this as a merge request.
--
You received this bug
The fix needs to be done in GTK4, not in cpdb-libs, as in cpdb-libs we
are settling now for a stable API and cpdb-libs is already used in other
print dialogs (Qt, LibreOffice, Chromium, Mozilla) and there we do not
want to re-introduce the unnecessary instance name.
--
You received this bug notif
The problem here is that the CPDB support for the GTK print dialog was
created in an early stage of the formation of the second-generation API
of CPDB. Some functions still had an instance name parameter and this
parameter got dropped later. So in the GTK code the calls have to get
corrected, remov
Gutenprint actually works on 32-bit. The Debian package is blocked for
32-bit via "architecture-is-64-bit" pseudo package (from architecture-
properties) in "build-depends:". I have removed this entry for the
Ubuntu package now, to that it gets built on 32-bit (currently only
armhf).
Entry of the
** Changed in: gutenprint (Ubuntu)
Status: Triaged => 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/2099865
Title:
FTBFS on armhf in the release pocket
To manage notifications
Jeffrey, thanks for your testing.
The `run-tests.sh` is meant to check whether cups-browsed's original
functionality of creating working print queues is working. Therefore I
never ran it repeatedly.
How often did you run your loop with the old version and with the new
version? Does the old versio
Sorry for posting a test case only focusing on the busy-loop bug going
away. Important is also that cups-browsed is still doing its original
functionality of automatically creating print queues for network
printers (IPP printers, remote CUPS queues, Printer Applications)
correctly.
At least nobod
*** This bug is a duplicate of bug 2049315 ***
https://bugs.launchpad.net/bugs/2049315
You should have a directory /var/crash and in it a file with a name like
_usr_sbin_cups-browsed.115.crash
The number in the name may be different for you.
Run
apport-bug /var/crash/_usr_sbin_cups
I have now tested with the script of @jeff250 on Oracular.
Unfortunately, a failure of cups-browsed does not stop the script, cups-
browsed gets killed after a timeout of 90 second.
So to capture failures I ran the following command from another
terminal:
while true; do sleep 2; ps aux | grep /u
** Tags removed: verification-needed verification-needed-oracular
** Tags added: verification-done verification-done-oracular
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049315
Title:
cups-browse
@mruffell, thank you very much!
I have installed the kernel 6.11.0-17-generic on my Oracular system now
and the ghost screen has gone away. All perfect now for me. Now I should
be able to do projections on conferences in Mirror mode without
problems.
$ uname -rv
6.11.0-17-generic #17-Ubuntu SMP P
Did you kill the old instance of cups-browsed, which was stuck on 200%
CPU, with
```
killall -9 cups-browsed
```
before doing the update?
If not, the update can take significantly longer. This is due to the
fact that on regular restarting of cups-browsed only the SIGTERM signal
(`kill -TERM`) is
*** This bug is a duplicate of bug 2049315 ***
https://bugs.launchpad.net/bugs/2049315
Please see bug #2049315 for a method to reproduce this bug, in the [
Test Plan ] section of the bug description.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
*** This bug is a duplicate of bug 2049315 ***
https://bugs.launchpad.net/bugs/2049315
Please see bug #2049315 for a method to reproduce this bug, in the [
Test Plan ] section of the bug description.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subs
** Description changed:
[ Impact ]
During the past months it often happened that a user observed that cups-
browsed takes 100% or 200% (2 cores) of CPU and ceases to do its actual
work. This even happens for users who do not print anything, just
printers shared by other computers in t
@jeff250, thank you very much! And also thanks a lot for finding a
method to reproduce the problem. I did not come to the idea that one
could hammer the daemon with restarts, was only thinking about remote
print queues.
So anybody else here, especially with an Oracular system, please do the
same t
*** This bug is a duplicate of bug 2049315 ***
https://bugs.launchpad.net/bugs/2049315
Firefox has a security feature which does prevents automatically
downloading http:// URLs from a page which is delivered via https://. To
actually do the download, you have to click the download symbol at th
*** This bug is a duplicate of bug 2049315 ***
https://bugs.launchpad.net/bugs/2049315
It can be that the mirrors take some hours until getting a certain new
package version. Please try again.
Also do not forget to run
sudo apt update
before your new attempt.
--
You received this bug
I have backported the fix from cups-browsed 2.1.1 also to the cups-
browsed packages of Noble (2.0.0-0ubuntu10.3) and Oracular
(2.0.1-0ubuntu2.2) and uploaded them.
As soon as these packages are accepted into the -proposed repositories,
testing instructions will get posted here. Please test then a
** Also affects: cups-browsed (Ubuntu Oracular)
Importance: Undecided
Status: New
** Also affects: cups-browsed (Ubuntu Plucky)
Importance: Undecided
Status: Fix Released
** Also affects: cups-browsed (Ubuntu Noble)
Importance: Undecided
Status: New
--
You received
For a quicker solution one possibility could be to go through the xdg-
desktop-portal, the way how Flatpaks print. Here one should perhaps
investigate the Flatpak of Chromium and see how printing in it works,
whether the Chromium print dialog is patched there to make use of the
portal or perhaps co
The problem here is how Chromium obtains the printer capabilities
(available paper sizes, trays, resolutions, duplex, ...) to display them
in the print dialog and give the user the possibility to choose from
them.
Chromium reads the capabilities from the printer's PPD files in
/etc/cups/ppd/QUEUE_
I have now followed my suspect what can have caused the 100%-CPU issue
in cups-browsed, that there was a global HTTP connection and it was used
by paralalizing threads. So I have done away with the global HTTP
connection:
https://github.com/OpenPrinting/cups-browsed/commit/a8b645e4b3
I have d
Reported to CUPS upstream:
https://github.com/OpenPrinting/cups/issues/1118
Thank you for the bug report and all the files.
** Bug watch added: github.com/OpenPrinting/cups/issues #1118
https://github.com/OpenPrinting/cups/issues/1118
** Changed in: cups (Ubuntu)
Status: Incomplete =>
** Summary changed:
- libcupsfilters2 2.0.0-0ubuntu7.1 ignores printers
+ CUPS passes illegal characters from PPD file to printer IPP attributes
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2089231
OK, thanks. Could you also attach the PPD file of your printer (should
be /etc/cups/ppd/copier3.ppd on the print server (cups1.bytec.de), the
machine where the printer is connected to, or do "wget
http://cups1.bytec.de:631/printers/copier3.ppd";).
The problem here is
1. The machine-readable strin
It seems that the most recent security update considers some attributes
of a legitimate printer invalid.
Could you do the following:
ipptool -tv ipp://cups1.bytec.de:631/printers/copier3
get-printer-attributes.test > copier3.txt
ipptool -tv ipp://cups1.bytec.de:631/printers/copier3_a3
get-print
The mentioned Apple bug report got already continued at OpenPrinting:
https://github.com/OpenPrinting/cups/issues/1072
What would be needed is that as reaction on a cups-pki-invalid error a
dialog gets popped up telling about the certificate change and asking
whether the physical printer is still
See especially
https://github.com/OpenPrinting/cups/issues/1072#issuecomment-2393434856
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1973441
Title:
Printing does not work on Ubuntu 22.04 - cups-pk
*** This bug is a duplicate of bug 2049315 ***
https://bugs.launchpad.net/bugs/2049315
** This bug has been marked a duplicate of bug 2049315
cups-browsed running non-stop on two cores
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
*** This bug is a duplicate of bug 2049315 ***
https://bugs.launchpad.net/bugs/2049315
** Summary changed:
- cups-browsed takes 2 CPU threds for nothing
+ cups-browsed takes 2 CPU threads for nothing
** This bug has been marked a duplicate of bug 2049315
cups-browsed running non-stop on t
In CUPS 2.4.10 the "make check" build test is not working and not
finding a fix I tried the already available (but not yet picked up by
Debian) 2.4.11 and the test worked there again, so CUPS on plucky is now
updated to 2.4.11.
--
You received this bug notification because you are a member of Ubu
*** This bug is a duplicate of bug 2049315 ***
https://bugs.launchpad.net/bugs/2049315
** This bug has been marked a duplicate of bug 2049315
cups-browsed running non-stop on two cores
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
@matthias-may, if you turn off browsing in cups-browed.conf but not in
cupsd.conf, does the problem (high CPU usage by cups-browsed) still
occur?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049315
I have added the above-mentioned part to the kernel command line (file
/etc/default/grub), done "sudo update-grub", and rebooted.
After that, the ghost screen is still there (I only had used the
temporary workaround before booting).
I have run
sudo dmesg > dmesg-boot-log-20241031.txt
to obtain
I have the same problem.
I bought a ThinkPad T14 gen 5 in May this year. Worked perfectly with
Noble, but now, after the evil Oracular Oriole has eaten the nice cute
Numbats, I got the ghost screen as described in this bug report. This is
very disturbing, starting from the mouse pointer not stoppi
Just disabling the ghost display in the System Settings was not helpful
for me, as with this the "Mirror" mode for the actual display and the
projector does not work. Probably this is another bug ...
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribe
The temporary workaround suggested in the initial description in the bug
report for NVidia, bug 2060268
-
[ Temporary Workaround ]
1. sudo rm /dev/dri/card0
2. Log in again.
-
also works here. I did not try the permanent workaround presented there,
but most probably it will also work.
E
Uploaded gutenprint 5.3.4.20220624T01008808d602-3ubuntu1 with the build
dependency on architecture-is-64-bit removed.
** Changed in: gutenprint (Ubuntu)
Status: New => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
There is no actual reason to exclude Gutenprint from 32-bit systems. The
exclusion on Debian is most probably lack of patience of the maintainer.
The Snap package continues to build on armhf, there seems to be no
upstream change having made this package 64-bit only.
We only need to remove any art
*** This bug is a duplicate of bug 2049315 ***
https://bugs.launchpad.net/bugs/2049315
In the upstream issue
https://github.com/OpenPrinting/cups/issues/879
this dhould have been fixed, but actually the change applied there seems
to be without effect.
** Bug watch added: github.com/OpenPrin
Done. Synced BleachBit 4.6.0-4 right now, thanks for investigating.
** Changed in: bleachbit (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2029480
Ti
** Also affects: rhythmbox (Ubuntu)
Importance: Undecided
Status: New
** Also affects: bleachbit (Ubuntu)
Importance: Undecided
Status: New
** Also affects: libreoffice (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are
No, the CUPS of 24.04 is 2.4.7.
I am have currently installed 2.4.8 from source and I will see if it
actually prevents the problem, but it will need some days to get good
evidence whether the bug is really fixed.
--
You received this bug notification because you are a member of Ubuntu
Bugs, whic
Please first remove any remainder from previous attempts:
cancel -a
cupsenable HP_ColorLaserJet_MFP_M278-M281
Could you then run the command
cupsctl --debug-logging
And do another print attempt. If it fails again, attach the following
files
/var/log/cups/error_log
/etc/cups/ppd/HP_ColorLaserJe
There is a known bug tat cups-browsed can be stuck in a busy loop, bug
2018504. Most probably it is stuck for you and so does not handle the
SIGTERM to shut down.
Usually cups-browsed's shutdown removes the local print queues which
cups-browsed has created and therefore we should not eliminate it
So you got the 200% on cupsd now, not on cups-browsed? Seems that cupsd
can run into a similar bug.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049315
Title:
cups-browsed running non-stop on two
These processes
-
$ ps aux | grep cups-browsed | grep -v grep
root 2912 0.0 0.0 2892 1708 ? Ss 10:13 0:00 /bin/sh
/snap/cups/1047/scripts/run-cups-browsed
root 3407 0.0 0.0 2892 892 ? S 10:13 0:00 /bin/sh
/snap/cups/1047/scripts/run-cups-browsed
-
come from the CUPS Snap. They are from a
CUPS 2.4.8 got released and the fix
https://github.com/OpenPrinting/cups/issues/879 is included.
Heinrich, thanks again for the investigations and bug report.
Heinrich, best would be to do an SRU of CUPS, applying the patch to
Ubuntu's 2.4.7 would be easy, but how does one verify this fix? Do you
Thanks everyone for posting logs here.
I would like to have another thing from everyone who runs into the
problem.
1. When you observe the problem, DO NOT kill cups-browsed.
2. Save the debug log and attach it to this bug report.
3. Determine the process ID (PID) of cup-browsed:
ps aux | grep
*** This bug is a duplicate of bug 2029480 ***
https://bugs.launchpad.net/bugs/2029480
** This bug has been marked a duplicate of bug 2029480
SyntaxWarnings with Python3.12
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https:
As I said in comment #4
-
The binary package libsane-hpaio DOES NOT depend on the binary package hplip,
not even indirectly, so the binary package hplip can get demoted to Universe.
the binary package printer-driver-hpcups also does not depend on the
binary package hplip, but printer-driver-
My upload got approved now:
https://launchpad.net/ubuntu/+source/cups/2.4.7-1.2ubuntu7
This means that the package is in noble-proposed now. The autopkgtests
of the package itself and its dependencies get run on all the 6
supported architectures. When they all pass, the package gets into
noble-re
I have uploaded it, but starting from beta freeze until the final
release all uploads have to be approved by the release team. As I have
done the upload on Friday late at night (CEST) there was probably nobody
of the release team around to pass this upload through. Probably this
will happen only on
Sorry, I completely overlooked that there were 2 fixes. I have applied
the patch of PR #935 now, too, and uploaded this as cups
2.4.7-1.2ubuntu7.
** Changed in: cups (Ubuntu)
Status: In Progress => Fix Committed
--
You received this bug notification because you are a member of Ubuntu
Bugs
1 - 100 of 14353 matches
Mail list logo
