Created attachment 698516 [details] file example Recent okular changes caused odd/event pages broken. Standard way to print two side document on a single side printer is to print event reversed pages, then odd direct. example ap.djvu: 1 2 3 4 xeven_reversed.pdf: should be 4 2 , actually 1 2 3 4 xodd_direct.pdf: should be 1 2 , actually 1 2 3 4 rpm -q okular okular-4.9.5-3.fc17.x86_64 It worked OK, it got broken during some update
There is a similar problem for a while in evince https://bugzilla.redhat.com/show_bug.cgi?id=730574 I just gave up on GNOME these gnome developers are arrogant freaks obsessed with changes for the sake of changes, incapable of fixing bugs (for years), and pushing 2x2 inches finger-touch interface to 30inch desktop. But now you kde guys started broking okular, it was working perfectly OK before. Please fix okular, because there is now no way in Fedora to print two side document on a single side printer.
I meant example ap.djvu: 1 2 3 4 xeven_reversed.pdf: should be 4 2 , actually 1 2 3 4 xodd_direct.pdf: should be 1 3 , actually 1 2 3 4
When you say "working perfectly OK before" and "broke during some update", at what point did things break? How long ago did it work?
And what format did it work with? Are you sure you tried it with DjVu? Printing in Okular is more backend-dependent than you'd expect, so this might be a backend bug.
A simple way to test: Try "printing" the DjVu (completely) to a PDF, then printing (to your actual printer, or for testing to another PDF) the page selections you want from the PDF. Does that work any better than printing the DjVu file directly?
It definitely worked at some point in F17. all version used: /var/log/yum.log-20130101:Jun 02 08:59:05 Installed: okular-4.8.3-1.fc17.x86_64 /var/log/yum.log-20130101:Jun 28 10:04:24 Updated: okular-4.8.4-1.fc17.x86_64 /var/log/yum.log-20130101:Aug 14 09:26:11 Updated: okular-4.8.5-1.fc17.x86_64 /var/log/yum.log-20130101:Aug 27 11:54:14 Updated: okular-4.8.5-3.fc17.x86_64 /var/log/yum.log-20130101:Sep 25 10:08:38 Updated: okular-4.9.1-1.fc17.x86_64 /var/log/yum.log-20130101:Oct 04 07:50:27 Updated: okular-4.9.2-1.fc17.x86_64 /var/log/yum.log-20130101:Nov 16 09:08:58 Updated: okular-4.9.3-1.fc17.x86_64 /var/log/yum.log-20130101:Dec 18 08:08:46 Updated: okular-4.9.4-1.fc17.x86_64 /var/log/yum.log:Jan 13 11:42:45 Updated: okular-4.9.5-1.fc17.x86_64 /var/log/yum.log:Feb 09 04:48:48 Updated: okular-4.9.5-3.fc17.x86_64 I think (but not sure ) that okular-4.8.4 & okular-4.8.5 worked. okular-4.8.3 should work almost definitely. In current okular printing .pdf .djvu .ps to file produce the same (broken) results in all formats. In evince .pdf is OK, .djvu & .ps are differently broken (you can check other bug report https://bugzilla.redhat.com/show_bug.cgi?id=730574 ) The broken results results were observed when printing to .pdf file. Then I printed directly to printer to my surprise the result is correct when printing both .djvu & .pdf even reversed: 4 2 odd direct: 1 3 but again, the output is correct only for printing directly to printer. Looks only "print to file" is broken.
Ot is also broken for printing .epub files. when printing .epub - "reverse order" is honoured, but even/odd is not. It prints everything. not even/odd. Can you fix that and not be like arrogant&lazy gnome people with evince https://bugzilla.redhat.com/show_bug.cgi?id=730574
Insulting developers is a VERY bad idea if you want them to fix bugs for you!
Agree, I was not right insulting gnome developers. Sorry for that. I just gave up on gnome about a year ago, because gnome developers became а sect listening only to themselves(unity) and making pointless changes for a sake of changes. I switched to KDE because of that and stopped caring about gnome, but because of some unconscious reason I offended gnome guys in this bug report. Sorry for that.
This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.