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: github.com/apple/cups/is
Exactly:
# lpstat -e
ECOSYS-P6026cdn
Kyocera_ECOSYS_P6026cdn
# lpstat -v
Device for ECOSYS-P6026cdn: socket://192.168.4.2
That makes sense to me - as I could swear that I really printed on a
printer, and later (maybe after rebooting, the next day etc) I try to
print on the same one, and it doe
First, here the new attrs.txt
** Attachment added: "attrs.txt"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+attachment/5248523/+files/attrs.txt
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-
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 s
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
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1813825
Title:
"driverless" print
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
Cust
@Clint, that seems another issue, could you maybe open a new bug about
that one?
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1813825
Title:
"driverless" printer wor
If I can expand upon duplex printing I have encountered an issue in the control
centre 18.10 too.
When enabling duplex in gnome-control-center it does not work,
$>lpoptions -l
...
Duplex/Two-sided: *None DuplexNoTumble DuplexTumble
...
but when doing so in system-config-printer it does
$>lpopt
I deleted all printers and waited for CUPS / driverless to find them again.
Here a few CLI outputs (which are small enough so I dare to spost them inline )
$ ls -1 /etc/cups/ppd/
Kyocera_ECOSYS_P6026cdn.ppd
Kyocera-ECOSYS-P6026cdn.ppd
Kyocera_ECOSYS_P6026cdn.ppd.O
Kyocera-ECOSYS-P6026cdn.ppd.O
$
Second file. The printer is added automatically twice. Maybe this is
because the printer has a print server, which exports the printer again
and announces it to the network? KM15881D.local is the network name of
the printer.
** Attachment added: "autogenerated 2. ppd file"
https://bugs.launchp
This file is named .0 because I have the printer installed with a custom
ppd file (from kyocera) manually - with the same name, so I think cups
adds the .0 automatically.
** Attachment added: "IPP PPD file"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+attachment
one shouldn't make promises. Follows ASAP. Give me a few days.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1813825
Title:
"driverless" printer workflow has bad usab
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
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
** Changed in: gnome-control-center (Ubuntu)
Status: Incomplete => New
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu.
https://bugs.launchpad.net/bugs/1813825
Title:
"driverless" printer workfl
First small thing: stopping cups-browsed dowsn't change anything. Even when
stopped, deleting a driverless printer lets it popup again after a few seconds.
Rest tomorrow.
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-c
First, driverless printers (automatically created queues for IPP
printers) can be generated by cups-browsed and by CUPS.
So as a first approach you could try to stop cups-browsed to see whether
you still get auto-created printers or not.
sudo systemctl stop cups-browsed
stops cu[ps-browsed and
It seems you used gdb just right yes.
I was expecting those warnings to print when you try to open the printer
options/details since those dialogs show empty and the warning looks
like they add with missing widgets. Oh well, thanks for trying :)
At this point we should wait for Till (who is the m
Ok; I never used gdb before, just visual debuggers.
I'm not sure this is not a blind alley. The "gtk_container_add warning" is not
reproducible and has IMHO nothing to do with this bug(s) (just IMHO).
As far as I understood, "b g_log" sets a breakpoint at the g_log() function,
right?
Just too un
Thanks for the info, the logs don't have much though :/
The journal has that
gnome-control-c[31150]: gtk_container_add: assertion 'GTK_IS_CONTAINER
(container)' failed
It would be interesting to get a backtrace of that warning, unsure if
you know your were around debugging enough to do that tho
** Attachment added: "cups_error_log"
https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1813825/+attachment/5234066/+files/cups_error_log
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-control-center in Ubu
I'm sorry to write "more than" one problems into one bug, but from a users POV
they are all the same - seen as "usability" bug. If you tell mo more how I can
help, I can also file separate ones if this is needed. But to gather
information, maybe it's best to leave it ATM as one?
Logs attached, i
Thank you for your bug report. Could you attach your journalctl log from a boot
where you triggered the issues described?
Could you also add your logs from /var/log/cups?
Till, do you have any idea about those issues?
** Changed in: gnome-control-center (Ubuntu)
Importance: Undecided => Low
Additionally, since "driverless" printing, I always have a printer named
"print" in my printing dialog, which I can't print to, and can't delete
neither. Print jobs are denied at any time there.
** Attachment added: "GNOME printing dialog"
https://bugs.launchpad.net/ubuntu/+source/gnome-contro
23 matches
Mail list logo