_usr_lib_cups_filter_pstops.7.crash

[Bili Joe Campbell]

Binary package hint: cupsys

Recently upgraded Ubuntu 7.10 to 8.04. On first boot, could not execute "sudo" commands ("Unable to resolve host "casi""). Also could not access Synaptic from menu. Second boot produced a flurry of 7 "Crash detected" reports, each opening a tab in Firefox on Launchpad. Each tab required that I log in, but, after the first tab I was already logged in. Subsequent tabs would not let me proceed without logging in, and when I did, all the bug report information was wiped off the page to display "You are already logged in", so all but one bug report was lost. The third boot rendered the system unusable (wouldn't finish booting because it could not locate the root filesystem, though the error message gave the correct UUID for my HDD. In any case, through some trickery, I have recovered much of the crash information for the remaining bugs. The report for this one is attached (as a text file). NOTE: All these crashes occurred during boot up, so I can't tell you what I was doing. What I expected to happen was a clean boot. What did happen was a boot accompanied by a flurry of "Crash detected" reports, that piled up, one on top of the other. The boot process did run to completion, however, and the screen looked normal, but the system behaved erratically. I hope this helps some.

Sincerely,
Bili Joe

ProblemType: Crash
Architecture: i386
Date: Sun Apr 27 16:45:24 2008
DistroRelease: Ubuntu 7.10
ExecutablePath: /usr/lib/cups/filter/pstops
NonfreeKernelModules: cdrom
Package: cupsys 1.3.7-1ubuntu3
PackageArchitecture: i386
ProcCmdline: Photosmart_3200 131 bili Upgrading\ your\ existing\ Ubuntu\ installation\ |\ Ubuntu 1 media=Letter\ sides=one-sided\ finishings=3\ number-up=1\ outputorder=reverse\ PrintoutMode=Draft\ job-uuid=urn:uuid:ab80f992-7805-37bc-6aac-78bab8091f6e /var/spool/cups/d00131-001
ProcCwd: /
ProcEnviron:
 PATH=/usr/lib/cups/filter:/usr/bin:/usr/sbin:/bin:/usr/bin
 LANG=en_CA
Signal: 11
SourcePackage: cupsys
Stacktrace:
 #0 0x0804dc6f in ?? ()
 #1 0x00000000 in ?? ()
StacktraceTop:
 ?? ()
 ?? ()
ThreadStacktrace:

Title: pstops crashed with SIGSEGV
Uname: Linux Casi 2.6.22-14-generic #1 SMP Tue Feb 12 07:42:25 UTC 2008 i686 GNU/Linux
UserGroups:

[Till Kamppeter (till-kamppeter)]

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?

[Javier Jardón (jjardon)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!