Firefox 3 No Printers Debian 64

[DarkDexter]

I've tested this on Debian 64 with Lenny and now Squeeze with the same results. When I run Firefox/Swiftfox/Firefox Beta and try to print something there are no printers listed. Whenever I try to open a print dialogue I get this from the command line:

(firefox-bin:14348): Gtk-WARNING **: /usr/lib/gtk-2.0/2.10.0/printbackends/libprintbackend-cups.so: wrong ELF class: ELFCLASS64

I've tried changing the printer in about:config to use lpr, kprinter, and gtklpr with no change in the problem. I'm assuming this is some kind of 64 bit issues does anyone know how to correct it?

[gamblor01]

Wow interesting. I have a 64-bit VM running Kubuntu that I could try to see if it works. I briefly "upgraded" my desktop to the 64-bit Ubuntu 8.10, but the lack of 64-bit application support caused me to revert back to the 32-bit mode (where everything now works again).

I don't remember if I got my printer working while running the 64-bit version or not, but I seriously doubt I ever tried to print anything from firefox. I'll have to try my Kubuntu 64-bit VM and see what happens. Also, I could even boot up the Ubuntu amd-64 live CD and see what happens. My only concern is that I print from a printer attached to my Mac via IPP. I'm not sure I'll encounter this same problem but I can try and then post the results.

Out of curiosity, what is the output of this command?


$ file /usr/lib/gtk-2.0/2.10.0/printbackends/libprintbackend-cups.so

[je_fro]

Maybe he's running a 32bit firefox (flash, java) and everything else is 64bit.

[DarkDexter]

dex@ThnkPd:~/Desktop$ file /usr/lib/gtk-2.0/2.10.0/printbackends/libprintbackend-cups.so
/usr/lib/gtk-2.0/2.10.0/printbackends/libprintbackend-cups.so: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, stripped


I am running Firefox 3.1 Beta 2 Downloaded off Firefox's site.

[JohnT]

A little insight on the subject...http://opensolaris.org/jive/thread.jspa?messageID=28523

[The Coder]

I am not getting this problem with my Debian Lenny x64 install and Iceweasel.

[DarkDexter]

Is there something I have to do with the libraries so that they have 32bit compatibility? Is it possible to use kprint in Firefox instead of its built-in printer manager? All of my KDE apps using kprinter don't have this problem.

[je_fro]

If you have a 64-bit browser, can you print from that?

[The Coder]

I am running Debian Lenny x64 using Iceweasel x64 using the HP 1012 printer connected directly with my machine using USB. How did you set up your printer? I used the CUPS web interface to do mine. Are you experiencing the same problem printing from other programs or is it just Firefox? I know there was a package I installed that, from what I read, that allows printing properly from Firefox. Let me see if I can find the name of the package for you. Also if you used CUPS to set up your printer, make sure to add your user to the list of users that have permission to use this printer. You do this right within the CUPS interface.

Edit: The package I am referring to is gtklp. DO you have that installed? I read an article that said that this package helps to allow printing through mozilla/firefox.

[bwkaz]

Is there something I have to do with the libraries so that they have 32bit compatibility? Yes -- install the 32-bit version of each of these libraries. There is no way to modify the 64-bit library file, though; you need to install a separate 32-bit library.

However -- Who decided to put the 64-bit libraries into /usr/lib? That's COMPLETELY wrong; LSB says to put 64-bit stuff into /lib64 and /usr/lib64 (but only for x86). And the 64-bit ABI requires /lib64/ld-linux-x86-64.so.2 (which is hardcoded into every single binary on the system, and cannot be changed), not /lib/ld-linux-x86-64.so.2 or something like that.

Sigh.

Is it possible to use kprint in Firefox instead of its built-in printer manager? All of my KDE apps using kprinter don't have this problem. That's not because they use kprint. That's because they're 64-bit. :p

You can't load a 64-bit library into a 32-bit process, and you can't load a 32-bit library into a 64-bit process.