[Expired for cups (Ubuntu) because there has been no activity for 60
days.]
** Changed in: cups (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
I wasnt able to get a backtrace because there was "no stack".
This is what shows in gdb:
Program received signal SIGABRT, Aborted.
__GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
50 ../sysdeps/unix/sysv/linux/raise.c: No such file or directory.
(gdb)
Continuing.
** Attachment added: "error_log"
https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1839446/+attachment/5281584/+files/error_log
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
Sorry, wrong bug, ignore that comment.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1839446
Title:
When trying to print a test page CUPS crashes
Status in cups package in
I've tested this on E, and I can now print in B and Colour again.
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to cups in Ubuntu.
https://bugs.launchpad.net/bugs/1839446
Title:
When trying to print a test page CUPS crashes
Could you follow the instructions of the section "CUPS error_log" on
https://wiki.ubuntu.com/DebuggingPrintingProblems to get an error_log in
debug mode from the CUPS crash?
Also some form of backtrace of the crashing CUPS daemon would be great
(apport record? cupsd run in a way that one can
6 matches
Mail list logo