pstops crashed with SIGSEGV

[Bili Joe Campbell]

Binary package hint: cupsys

I don't know if this is a new bug or not. Three messages popped up so fast I didn't have time to read them, then Firefox opened up three launchpad sessions, all asking me to log in. I logged into this one, but when I went to the other tabs and tried to log in, it told me that I was already logged in and erased all the information about the crashes it had just reported. All I know is I just upgraded from 7.10 to 8.04 and now every time I log in I get pummeled with crash reports, and I can't "sudo" any more, so I am now logged in as root, in order to get access to synaptec so I can re-install "locate" so I can find my menu.lst file, so I can modify it so I can see what the ____is going on during boot up (I'm sure I have its location in my notes, but I still want "locate", which I used to have). I'm about ten minutes away from hosing this installation, and restoring from the backup I am SOOO glad I made, before I started this upgrade. What in the Blue Blazes is happening? I thought this was a post-beta, release-ready version. I thought it was only Microsoft that was cruel enough to make their users finish Beta testing for them. PLEASE GET THIS FIXED!!!

<email address hidden>

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)]

Can you post the file which you have sent to the printer so that pstops crashed? pstops is a print filter and so it only gets executed when something is sent to the printer.

[Bili Joe Campbell (bilijoe)]

First off, this was under a fresh upgrade to 8.04, NOT 7.10. As far as the printer is concerned, I don't think "I" was sending anything to the printer, but the system issued a flurry of crash reports--so fast they piled up and I couldn't respond to them all and even lost track of which notification window went with which crash report. It also opened Firefox, and opened the Launchpad sign in window for each crash, in rapid succession. Two bug reports got lost, because, after I signed in and dealt with the topmost one (I assume the last one), the other screens wouldn't let me do anything until I logged in--but I was already logged in, so when I tried to log in again (which was the only thing it would let me do), it posted a notice that I was already logged in, which overwrote the bug report information that had been on the screen, and the "back" button just took me back to the sign in screen. So, like I said, two bug reports got lost in the scramble. I've never seen such a flurry of crash reports before. There must have been five of them inside ten seconds or less. I simply got overwhelmed and lost track. Sorry. in my panic, I may have tried to capture the reports that were being overwritten, by trying to print them--I don't remember. And there is no unaccounted for pages from my printer, so, if I did try to print, nothing got printed. Actually, at that point, I don't think my printer was available--I think the only option was to print to a PDF file. Attached is a list of the PDF files currently on my system. I'm pretty sure I didn't [intentionally] create any of them, so any that are not a "normal" part of the system or some software package, may be what triggered the "print" activity. I wish I could offer you more information, but I simply got caught off guard by all the crashes on the first boot of an upgraded system. I have multiple problems now, but I don't think any of them is related to printing. I just printed a test document, and it went OK, except now, I get a very different window when I select "print". Besides listing my printer, it lists "Print to File" (which is the default), PDF, and then the printer. When I select the printer, almost all the options (like "print selection", "Print range of pages", Printer Setup", etc., are grayed out. I seem to only have the option to print the entire file, with the default settings. I hope some of this helps. I'm fried, and may go back to 7.10, if I can't get things working right today.

[Till Kamppeter (till-kamppeter)]

pitti, can you help the poster of this bug to recover all his crash reports?

[Bili Joe Campbell (bilijoe)]

I added some information to my report, and attached a list of possible "culprit" files. Please look there for the info. Thanks.

BiliJoe
 -------------- Original message ----------------------
From: Till Kamppeter <email address hidden>
> Can you post the file which you have sent to the printer so that pstops
> crashed? pstops is a print filter and so it only gets executed when
> something is sent to the printer.
>
>
> ** Changed in: cupsys (Ubuntu)
> Status: New => Incomplete
>
> --
> pstops crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/223495
> You received this bug notification because you are a direct subscriber
> of the bug.

[Martin Pitt (pitti)]

To walk through the crash reports one by one it should be enough to open /var/crash/ in the file browser and click on the ones you want to report (the ones which happened as your user, at least). However, apport is not supposed to report all at the same time (it doesn't do that here), so I wonder what's wrong on your system.

What is the output of

  ls -l /var/crash

? What happens if you do

  sudo touch /var/crash/*

? You should get notifications about the crashes, with an offer to submit them (they shouldn't open firefox tabs straight away).

[Bili Joe Campbell (bilijoe)]

Unfortunately, I cannot give you this additional information. I wish I could, but, after a couple more glitchy reboots, the system is now completely dead. It seems it can no longer find the root file system. It reports a correct UUID, but then says it doesn't exist. I waded through the script files, and found where the message was coming from, but it used a #DEFINE for the name/UUID of the filesystem, and I couldn't find where the value was assigned to that variable. It dumps me into a shell (one I am not familiar with), and I am tired of fudging around trying to get a system I already know is fraught with problems to start--it wasn't really usable anyway. My plan now is to install a clean copy of 7.10, and then restore my backup over that. It was when I tried to restore the backup over the messed up 8.04 that things really went South. I got a message that there were upgrades available (after the "restore"); there were 664 of them. I let them install, but several gave me t
he message I couldn't "upgrade" from 8.04 to 7.10. For an install on another machine, I downloaded the ISO file (for 8.04), but came up with a bad MD5 check. A second try got me a clean download, and resulted in a clean disk, and [apparently] a clean install (this one is the 64 bit version, the other was the i386 version). So, I am guessing that, if I got a glitched download of the ISO file, I very well might have gotten a glitched download of something during the upgrade. So, I'm going to try to get back to where I started, and try the whole thing again. If I have any problems the second time, I'll take more complete notes, and try to get you better information to work with. For now, I'm going to blame it on corrupted data coming in from the internet, during the upgrade. Thanks for your help, and let me know if there is anything more I can do for you.

Sincerely,
Bili Joe
 -------------- Original message ----------------------
From: Martin Pitt <email address hidden>
> To walk through the crash reports one by one it should be enough to
> open /var/crash/ in the file browser and click on the ones you want to
> report (the ones which happened as your user, at least). However, apport
> is not supposed to report all at the same time (it doesn't do that
> here), so I wonder what's wrong on your system.
>
> What is the output of
>
> ls -l /var/crash
>
> ? What happens if you do
>
> sudo touch /var/crash/*
>
> ? You should get notifications about the crashes, with an offer to
> submit them (they shouldn't open firefox tabs straight away).
>
> --
> pstops crashed with SIGSEGV
> https://bugs.launchpad.net/bugs/223495
> You received this bug notification because you are a direct subscriber
> of the bug.

[Jayson Rowe (jayson.rowe)]

Since it's been a very long time since any additional info was added to this bug, I'm just checking to see if this is still an issue, and find out what additional work should be done on this bug.

[Victor Vargas (kamus)]

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!