I can't print anymore from libreoffice-bin after a world update, including cups and libreoffice-bin. (350m1-Build2)
however i can print from opera, midori, texstudio, leafpad and epdfview and gimp.
I tried all printers i have availible, including the cups pdf printer. Nothing.
I'm sorry, but that's about all information i can give.
I have turned on debug logging in cupsd.conf and restarted cups, however klicking "print" in libreoffice doesn't create any reaction in cups. There is exactly NO new line in the complete /var/log/cups/*, neither in syslog. Sync didn't help either.
The following packages somehow could relate to this problem:
# emerge -pv1 ghostscript-gpl cups libreoffice-bin
These are the packages that would be merged, in order:
Calculating dependencies... done!
[ebuild R ] net-print/cups-1.5.2-r4 USE="X acl dbus gnutls jpeg png python ssl threads tiff -avahi -debug -filters -java -kerberos -ldap -pam -perl (-selinux) -slp -static-libs -usb -xinetd" LINGUAS="de -da -es -eu -fi -fr -id -it -ja -ko -nl -no -pl -pt -pt_BR -ru -sv -zh -zh_TW" 0 kB
[ebuild R ] app-text/ghostscript-gpl-9.05-r1 USE="X cups dbus djvu gtk idn jpeg2k -bindist -static-libs" LINGUAS="-ja -ko -zh_CN -zh_TW" 0 kB
[ebuild R ] app-office/libreoffice-bin-184.108.40.206-r1 USE="cups java (-aqua) -debug -gnome -kde" 0 kB
Does anybody have an idea where the problem could be?
Additional Info I forgot:
- compiling cups with USE="$USE debug" doesn't yield a single error message, too.
- print into file works
- export to pdf works
Firstly you don't need to add yourself to CC when you create bug, you get the mail anyway :-)
Also I tried the printing with binary version here right now and it printed me nice 4 page document, so something is really fishy.
Could you try the libreoffice-bin-220.127.116.11 (currently in testing)?
And if you have cpu cycles to spare you could try the non binary version (sadly I have no idea what might be wrong).
CCing printing even if it is basically the same team just for the semantic :-)
Guess what -
Yesterday just somewhere in between a lot of playing around with printer settings in libreoffice it DID print two jobs. On the first one, all printers i had vanished in return for a "generic printer" that worked. Then all printers reappeared and i could select a working one for my second successful job.
After that, no printer worked.
I have upgraded to libreoffice-bin-18.104.22.168, but it has the same behavior here.
Cups is "unemployed" - it gets no jobs...
Is this still a problem with libreoffice-bin-3.6 ?
Which version of cups are you using?
the problem 100% persists in libreoffice-bin-22.214.171.124.
[ebuild R ] net-print/cups-1.5.2-r4 USE="X acl dbus gnutls jpeg png python ssl threads tiff -avahi -debug -filters -java -kerberos -ldap -pam -perl (-selinux) -slp -static-libs -usb -xinetd" LINGUAS="-es" 0 kB
[ebuild R ] app-office/libreoffice-bin-126.96.36.199 USE="cups java (-aqua) -debug -gnome -kde" 69,574 kB
Maybe related maybe not.........I have had trouble for some time now printing from libreoffice-bin. If I open a document and print it immediately, it gets sent to cups and the job is printed. However if I modify the document first and save it and than print it. Printing fails every time. The job appears in cups as stopped, but I can't get cups to print the job even as the superuser. No useful errors are reported by cups. I have several Gentoo workstations. This happens in both openoffice-bin and libreoffice-bin. I thought it might be related to a bug in openoffice-bin so I switched my personal workstation to libreoffice-bin but the problem persists.
My printer always shows up in libreoffice-bin but printing to it can only be done by opening one document at a time and printing it before modifying or opening a second document. Very annoying...........
I had to switch to libreoffice-(source) due to dependency problems with recent boost changes but haven't had the time to see if the problem is there as well.
What about now? Do you still have problems with stable 188.8.131.52 or ~unstable 184.108.40.206?
in libreoffice-bin 220.127.116.11, the current status is:
printing the first time does not work under the previously described circumstances.
If I retry within 5 minutes, it works.
If I stop printing for > 5 min it doesn't work anymore, the next tries after that within a 5 minute frame after the last printing action however work.
Now Upgrading to 18.104.22.168.
Let's see what happens.