Slackware 13.1 first batch of updates - print crash on firefox and thunderbird
 

Well, that's about it - the firefox and thunderbird packages included on the first batch of official 13.1 updates keep crashing when I try to print a web page or an e-mail. Seamonkey, updated as well, can print as usual.

Any thoughts?

start a session from the console and then see if any errors get displayed, check your logs and see if they're providing additional details.

No error output on console.

Here's the crash report, I tried to print the default start page:

Add-ons: {972ce4c6-7e08-4474-a285-3208198ce6fd}:3.6.6
BuildID: 20100625222733
CrashTime: 1277755222
EMCheckCompatibility: true
FramePoisonBase: 00000000f0dea000
FramePoisonSize: 4096
InstallTime: 1277752415
ProductName: Firefox
ReleaseChannel: release
SecondsSinceLastCrash: 1022
StartupTime: 1277755215
Theme: classic/1.0
Throttleable: 1
URL: http://www.google.com.br/firefox?cli...en-US:official
Vendor: Mozilla
Version: 3.6.6

Same here except it seems it's any mozilla apps including Seamonkey ...

Started from the console I get the following error when printing:

bash-4.1$ seamonkey
/usr/lib64/seamonkey-2.0.5/run-mozilla.sh: line 131: 4782 Segmentation fault "$prog" ${1+"$@"}

Have removed all plugins and disabled most of my extensions but no go ...

And for the worst part, when I tried to downgrade firefox, thunderbird, and seamonkey (ie, reinstalling the packages on the DVD) the problem persists! How come...?

:banghead:

I just printed a web page and an email without incident. Did you upgrade both cups and ghostscript as well?

mlangdn,

Yes, I did upgrade cups and ghostscript, and I can print from within seamonkey. Ah, I'm on a 32-bit machine.

Same problem here on a 64-bit system.

edit: Tried the latest nightly binary distributed from mozilla.org, that one crashes on printing too.

Prints OK from both on Slackware64-13.1 (multi-lib).

samac

I think I found the problem - I had gnome-vfs 2.24.3 installed, removed it and the printing issues were over.

Does anybody else who's had this problem has a gnome-vfs installed too?

You're right, I had gnome-vfs 2.24.2 installed and after removing it, it works.

Wow sljunkie, worked for me too - how'd you find that out?

Hey rpedrica,

I created a new account to test how firefox would behave, and the console complained something about ~/.gnome and gnome-vfs... that was the clue I needed ;)

I believe that the real problem is that firefox and thunderbird are distributed as static binaries.

This problem does not exist on my Slackware 13.0 box with FF 3.6.6 and gnome-vfs-2.24.1.

/hoping to get a patch to apply to my slack 13.1 system soon

No problem in my 13.0 installation with gnome-vfs 2.24.1 either. It's only a problem with 13.1 for some reason.

The problem exists only with the latest cups 1.4.4 update. Going back to 1.4.3, printing works fine again, even with gnome-vfs or other gnome packages installed. This is probably a bug with firefox not interfacing with cups 1.4.4 properly, that only surfaces when certain gnome packages are installed.

This is a strange one:

http://www.cups.org/str.php?L3606

CUPS people blaming Mozilla for the bug (not gnome-vfs). I have the latest GSB gnome-vfs package installed with Firefox 3.6.6, and using cups-1.4.3. Printing works.

Upgrading to cups-1.4.4 and removing gnome-vfs also works. Hmmm.

I get the same with the different package combinations.

Remove ~/.gnome/gnome-vfs as well
 

Me too. Along with the removal of the old gnome-vfs, I had also to rm -rf ~/.gnome/gnome-vfs.

Seamonkey suffered the same problem, also.

But, thanks, it worked!

Luiz

Mozilla fix
 

Ok, it appears that the last batch of updates took care of the problem.

:)

I still can't print from firefox. It's not the same crash, but firefox doesn't see my printer even though it's visible to the rest of the system and working fine.

Crap, you're right. Updated to firefox 3.6.8 and the crash returned back from the dead.

:confused:

Same problem here. I have never had gnome-vfs installed, as far as I can tell. But I tried Chromium, and had to install orbit2 and gconf as dependencies. Not exactly sure, if this caused the problem, though, because after removing these packages and the configuration files the print crash problem in Seamonkey 2.0.6 is still there.

I am on Slackware64-13.1-stable, BTW.

gargamel

cups-1.4.4 -> cups-1.4.3 downgrade worked for me
 

seamonkey 2.0.6 (adblock-plus 1.2.2, betterprivacy 1.48.3, enigmail 1.0, flashblock 1.3.16, all active)

slackware 13.1/64 (no multilib), hplip-3.10.2, xfce 4.6.1

For me it helped to recompile CUPS against GNU TLS and disable to compile against OpenSSL. Don't know if I need any of them at all, but after that the crashes were gone :)

gnomeslackbuild
 

i had this problem when using slackware64 13.1 + gnomeslackbuild

now i see what the problem was

Has anyone informed the Mozilla and CUPS guys of this workaround? Maybe, if they know it, they can prepare updates of their software...

gargamel

I for sure didn't notice them. I found this advice a week ago somewhere else but don't remember where it was :(

https://bugzilla.mozilla.org/show_bug.cgi?id=573039

As you can see linking against gnutls has been the work around to this problem since end of July / beginning of August.

Question: is Patrick et. al. going to release a new build of Cups 1.4.4 linked against gnutls for Slackware 13.1?

I used Suse 10,2 and now using 11.3 with FF 3.6.8 and TB 3.1.3 -- and KDE ... no problem observed so far. Only one with Suse 10.2: when printing out of FF the printfile never was closed unless I shut down FF. But with 11.3. this problem is gone ...

Any comment from the Slackware team on this? Patch planned?

UP!?

The solution is to apply this patch http://www.linuxfromscratch.org/patc...ocking-1.patch to cups 1.4.4 and recompile it.

This way, you can keep gnome-vfs and use cups 1.4.4 and printing works again.

This fixes the problem at least here with :
- Slackware64-current
- firefox 4.0b7
- cups 1.4.4

It has still to be confirmed on :
- slackware 13.1
- slackware64 13.1
- slackware-current

With both firefox 3.6 and 4.0beta

cups has been upgraded to 1.4.5, but this bug is not fixed yet.

However, I can confirm that Bourdieu's patch works with cups 1.4.5 and 13.1, both in 32 and 64bits.

Fixed.
 

A new cups package has been uploaded which fixes this problem - http://slackware.osuosl.org/slackwar..._slack13.1.txz

Thank you, Patrick.