Unfortunately, this report does not contain any stack trace information.
So we will not be able to reproduce the bug with this information.
What happened is that a print job got executed which was still in the
queue when the reboot was done. Can you remember which file you tried to
print before rebooting? Can you print it again? Does it print normally
then? Or does the crash also happen this way? Does the crash still
happen with the newest Intrepid?
** Changed in: cupsys (Ubuntu)
Status: New => Incomplete
--
_usr_lib_cups_filter_pstops.7.crash
https://bugs.launchpad.net/bugs/224839
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
