Claws-mail does not print. The print job does not show in the Windows 7 print job queue. Nothing is being printed.
cannot confirm. I am printing daily. W10 + 3.13 + LAN printers.
Did it work for you in Claws Mail 3.12 (if you used it)? Could you run "claws-mail.exe --debug" try printing something, exit the application and provide content of claws-win32.log from your account's Temp folder? (The dir should be somewhere in your "Application Data" folder.)
Created attachment 1578 [details] Log Log was found in C:\user\AppData\Roaming\Claws-Mail\tmp Debug was started in CMD at C:\Program Files (x86)\Claws-Mail>claws-mail.exe --debug
The attached file is 3 bytes large, and contains only one word, "foo". Before printing, do you see a print dialog where you can select which printer to use and other settings? If so, the fault is not in Claws Mail.
(In reply to comment #4) > The attached file is 3 bytes large, and contains only one word, "foo". > Stating the obvious. What does "foo" stand for and mean? I presume it is an abbreviation of foomatic, a configurable printing filter. > Before printing, do you see a print dialog where you can select which > printer to use and other settings? Yes, printer shows as ready to print. > If so, the fault is not in Claws Mail. Print jobs of other applications are executed flawlessly. My understanding is that the print job is passed by the application to the spooler and from there to the printer. I suspect that the hand over of print job from claws-mail to spooler is faulty because no claws-mail print job ever shows in the spooler. However, print jobs of other applications show in the spooler and are executed. Logically questioning your statement, how can you be absolutely sure the fault is not in Claws Mail? Can you advise how you obtain a detailed debug report on Windows 7 64 bit, which additional debug software you install (32 or 64 bit on 64 bit system) and what steps do you follow?
You probably found wrong file. The string "foo" is situationally written into a file named "claws-crashed", not into the log file. claws-win32.log, when running claws-mail.exe --debug should start with something like this: claws.c:102:Starting Claws Mail version Claws Mail 3.13.0 main.c:769:runtime GTK+ 2.24.28 / GLib 2.45.2 main.c:777:buildtime GTK+ 2.24.28 / GLib 2.45.2 main.c:786:Compiled-in features:
(In reply to comment #6) > You probably found wrong file. The string "foo" is situationally written > into a file named "claws-crashed", not into the log file. claws-win32.log, > when running claws-mail.exe --debug should start with something like this: > > claws.c:102:Starting Claws Mail version Claws Mail 3.13.0 > main.c:769:runtime GTK+ 2.24.28 / GLib 2.45.2 > main.c:777:buildtime GTK+ 2.24.28 / GLib 2.45.2 > main.c:786:Compiled-in features: I found the wrong file. Path to file claws-win32.log on Windows 7 is C:\Users\User\AppData\Local\Temp .
Created attachment 1585 [details] claws-win32.log
Comment on attachment 1585 [details] claws-win32.log OK, so unfortunately there is nothing in the debug log that would help pinpoint the issue. I can print just fine, and I am getting the same debug lines, including the harmless "printing.c:1353:Error generating attribute list." message. Does at least printing to a file work? Either vie some PDF-export virtual printer, or to Postscript format via "Print to file" checkbox in the Windows printing dialog.
You could also try installing and printing from some other Windows application that uses GTK+, although I can't think of any at the moment. Maybe GIMP or Pidgin? In case printing ends up working from those, we could try and figure out what GTK+ version they are using, and go from there.
Created attachment 1587 [details] print to file
(In reply to comment #9) > Does at least printing to a file work? Either vie some PDF-export virtual > printer, or to Postscript format via "Print to file" checkbox in the Windows > printing dialog. Attached print to file. It does not contain the email printed but something else. When checking print to file in Claws Mail, a new window opens where only a file name can be put in but no location can be set to save file to. I needed to run a search to find file in C:\Users\User\AppData\Roaming.
Comment on attachment 1587 [details] print to file Hm, that looks like an empty job - a request to print nothing at all. This means that either Claws Mail sends an empty print job, or that job's content gets eaten somewhere within GTK.
(In reply to comment #10) > You could also try installing and printing from some other Windows > application that uses GTK+, although I can't think of any at the moment. > Maybe GIMP or Pidgin? > > In case printing ends up working from those, we could try and figure out > what GTK+ version they are using, and go from there. There must be an easier way to query the installed GTK+ version without having to install more software. Installed is GTK+ Runtime 2.12.8. Claws Mail about system information shows GTK+ 2.24.28 / GLib 2.45.2 and Win32--although it's actually 64 bit Windows. Do I need to uninstall GTK+ Runtime 2.12.8 and install http://gtk-win.sourceforge.net/home/index.php/Main/Downloads Latest Runtime and Theme Packages which today is gtk+-2.24.10? Would that have any negative effect on other installed software like GnuPG?
Claws Mail uses its own GTK+ library, and as far as I know, so does Gpg4win. You could try uninstalling the "GTK+ Runtime" package temporarily, perhaps there is some interference where "our" GTK+ uses some files from the Runtime package.
(In reply to comment #14) > > There must be an easier way to query the installed GTK+ version without > having to install more software. Installed is GTK+ Runtime 2.12.8. Claws > Mail about system information shows GTK+ 2.24.28 / GLib 2.45.2 and > Win32--although it's actually 64 bit Windows. > > Do I need to uninstall GTK+ Runtime 2.12.8 and install > http://gtk-win.sourceforge.net/home/index.php/Main/Downloads Latest Runtime > and Theme Packages which today is gtk+-2.24.10? > Would that have any negative effect on other installed software like GnuPG? I seem to remember from years back that there was a buffer overflow in the print functions in GTK+ which showed exactly your symptoms. Maybe your printing in some strange ways use your old GTK+ library. Is there a specific reason to have this old GTK+ library installed? If there is no reason you might as well uninstall it.
(In reply to comment #16) > I seem to remember from years back that there was a buffer overflow in the > print functions in GTK+ which showed exactly your symptoms. Maybe your > printing in some strange ways use your old GTK+ library. Is there a specific > reason to have this old GTK+ library installed? If there is no reason you > might as well uninstall it. It seems very likely. I tried installing it (and enabling the installer option to add the GTK Runtime path to system PATH), and afterwards Claws Mail was quite unstable, lot of freezing.
(In reply to comment #16) > (In reply to comment #14) > > > > There must be an easier way to query the installed GTK+ version without > > having to install more software. Installed is GTK+ Runtime 2.12.8. Claws > > Mail about system information shows GTK+ 2.24.28 / GLib 2.45.2 and > > Win32--although it's actually 64 bit Windows. > > > > Do I need to uninstall GTK+ Runtime 2.12.8 and install > > http://gtk-win.sourceforge.net/home/index.php/Main/Downloads Latest Runtime > > and Theme Packages which today is gtk+-2.24.10? > > Would that have any negative effect on other installed software like GnuPG? > I seem to remember from years back that there was a buffer overflow in the > print functions in GTK+ which showed exactly your symptoms. Maybe your > printing in some strange ways use your old GTK+ library. Is there a specific > reason to have this old GTK+ library installed? If there is no reason you > might as well uninstall it. Uninstalled GTK+ Runtime 2.12.8, rebooted system and print job still fails.
What is value of your system's PATH variable? You can check it in a cmd.exe window with "set" or "echo %PATH%". if I remember correctly, Gpg4win also does some PATH modifications for its libraries, and we had one or two bug reports for Claws Mail crashes caused by this.
Can you try changing the starting work directory of your Claws Mail desktop shortcut (the "Start in:" field) to wherever you installed Claws Mail? By default it should be "C:\Program Files (x86)\Claws Mail" on a 64-bit Win7. That way, we should rule out any foreign GTK+ or other library versions, since Windows is looking at current working directory first, when looking for libraries. This (starting directory) is something that I will change in next release whether it helps here or not.
(In reply to comment #20) > Can you try changing the starting work directory of your Claws Mail desktop > shortcut (the "Start in:" field) to wherever you installed Claws Mail? By > default it should be "C:\Program Files (x86)\Claws Mail" on a 64-bit Win7. > > That way, we should rule out any foreign GTK+ or other library versions, > since Windows is looking at current working directory first, when looking > for libraries. > > This (starting directory) is something that I will change in next release > whether it helps here or not. Done that and nothing changes.
Created attachment 1593 [details] set path information
(In reply to comment #19) > What is value of your system's PATH variable? You can check it in a cmd.exe > window with "set" or "echo %PATH%". if I remember correctly, Gpg4win also > does some PATH modifications for its libraries, and we had one or two bug > reports for Claws Mail crashes caused by this. Added attachment set path information.
Problem persists. Upgraded to claws-mail 3.14.0 and installed Gpg4win Version 2.3.3.
Browsing through tickets and figured I'd try and see if I could reproduce this problem since I"m running close to the same system. I can't. I'm running Windows 7 x64, Claws 3.14.0, I also have gpg4win 2.3.3 installed. I was able to print without problem.