GNOME Bugzilla – Bug 304223
used the godaddy website generated print page button and printing caused crash, (program galeon stopped)
Last modified: 2009-02-14 19:31:30 UTC
Distribution: Debian 3.0 Package: galeon Severity: normal Version: GNOME2.8.1 1.3.20 Gnome-Distributor: Debian Synopsis: used the godaddy website generated print page button and printing caused crash, (program galeon stopped) Bugzilla-Product: galeon Bugzilla-Component: general Bugzilla-Version: 1.3.20 BugBuddy-GnomeVersion: 2.0 (2.8.0) Description: Description of the crash: program galeon stopped Steps to reproduce the crash: 1. start galeon pointing to my default page, cups print system webserver 2. command it to print from the pulldown menus -- two ways tested... to printer that works when you do lp -d okipage14e file.ps to file... 3. observe it die.... it dies without a trace when I ask it to print to the printer, and if I ask for a file, it gives the option to Expected Results: How often does this happen? Whenver I forget and try to print a website receipt... (I have created a habit that galeon does not print, so I don't ask it to except by accident.) Additional Information: firefox prints fine. the interface is different - printer listed as Postscript/okpage14e and if youask to see details, you see the command lp -d okipage14e Debugging Information: Backtrace was generated from '/usr/bin/galeon' (no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1". (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...[Thread debugging using libthread_db enabled] [New Thread -1225915424 (LWP 6028)] [New Thread -1254847568 (LWP 6038)] [Thread debugging using libthread_db enabled] [New Thread -1225915424 (LWP 6028)] [New Thread -1254847568 (LWP 6038)] [Thread debugging using libthread_db enabled] [New Thread -1225915424 (LWP 6028)] [New Thread -1254847568 (LWP 6038)] (no debugging symbols found)...[New Thread -1237886032 (LWP 6033)] (no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...(no debugging symbols found)...0xffffe410 in __kernel_vsyscall ()
+ Trace 59676
Thread 1 (Thread -1225915424 (LWP 6028))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-05-15 02:10 UTC -------
What mozilla version are you using (you can find out by typing "about:" in the location entry in galeon)
Closing this bug report as no further information has been provided. Please feel free to reopen this bug if you can provide the information asked for. Thanks!
"What mozilla version are you using?" Galeon version is now 2.0.0 from debian package galeon 2.0.0-1 and galeon-common 1.3.21-6 Maybe this is a debian bug? Symptoms today are different too... no crash, just failed print. I print to pdf, then print that to get results. Next I upgrade both and test again... uh... may not be a complete test, since I am doing this bug report with galeon, and updating it wont affect the running copy in RAM... I'll add another comment later if the separate galeon instance I will do the test with somehow is affected by this open old one with wrong installation...package galeon 2.0.0-1 and galeon-common 1.3.21-6. The situation with this instance of galeon still open is failed print to the printer with the menu pick in galeon, but good print to the cups-pdf printer with a menu pick in galeon. The resulting pdf can be sent to the printer and prints fine. Failed print means printing starts, but the paper jam light comes on,a nd the macine needs a reset to continue.
The mozilla version installed along with galeon when printing fails is mozilla-browser 1.7.12-1 debian package.
Doesn't crash with gtk-print backend