[okular] [Bug 398443] okular sometimes goes into a state where "space" is recognized for navigation, but not "delete" or "pageup/pagedown"

https://bugs.kde.org/show_bug.cgi?id=398443 --- Comment #3 from Frederick Eaton --- Yes indeed, that does the trick. Thank you. I must have missed it before. -- You are receiving this mail because: You are watching all bug changes.

[okular] [Bug 398442] New: okular doesn't respect page reverse setting of PPD or lpadmin

https://bugs.kde.org/show_bug.cgi?id=398442 Bug ID: 398442 Summary: okular doesn't respect page reverse setting of PPD or lpadmin Product: okular Version: 1.5.1 Platform: Other OS: Linux Status:

[okular] [Bug 398443] New: okular sometimes goes into a state where "space" is recognized for navigation, but not "delete" or "pageup/pagedown"

https://bugs.kde.org/show_bug.cgi?id=398443 Bug ID: 398443 Summary: okular sometimes goes into a state where "space" is recognized for navigation, but not "delete" or "pageup/pagedown" Product: okular Version: 1.5

[okular] [Bug 398443] okular sometimes goes into a state where "space" is recognized for navigation, but not "delete" or "pageup/pagedown"

https://bugs.kde.org/show_bug.cgi?id=398443 Frederick Eaton changed: What|Removed |Added CC||frede...@ofb.net --- Comment #1 from

[okular] [Bug 398442] okular doesn't respect page reverse setting of PPD or lpadmin

https://bugs.kde.org/show_bug.cgi?id=398442 --- Comment #2 from Frederick Eaton --- $ pacman -Q qt5-base qt5-base 5.11.1-2 Steps: 1. Configure a printer to reverse pages (using PPD or lpadmin) 2. Print something in Okular 3. The pages come out non-reversed. I would have expected them to be

[okular] [Bug 398442] okular doesn't respect page reverse setting of PPD or lpadmin

https://bugs.kde.org/show_bug.cgi?id=398442 Frederick Eaton changed: What|Removed |Added CC||frede...@ofb.net -- You are receiving this

[okular] [Bug 398442] okular doesn't respect page reverse setting of PPD or lpadmin

https://bugs.kde.org/show_bug.cgi?id=398442 --- Comment #3 from Frederick Eaton --- After a full system upgrade (to fix printing), I confirmed that the bug still exists. This is for printing on paper, and configuring reversal using 'lpadmin' (i.e. printers.conf). Evince reverses, Okul

[okular] [Bug 398442] okular doesn't respect page reverse setting of PPD or lpadmin

https://bugs.kde.org/show_bug.cgi?id=398442 --- Comment #4 from Frederick Eaton --- Also I can again reproduce this with cups-pdf, so you don't need a printer. 1. Install cups-pdf 2. Add a printer via the CUPS interface, and select CUPS-PDF 3. Select the cups-pdf PPD /usr/share/cups/model

[okular] [Bug 398442] okular doesn't respect page reverse setting of PPD or lpadmin

https://bugs.kde.org/show_bug.cgi?id=398442 --- Comment #7 from Frederick Eaton --- > Can you confirm it's also working as you'd expect when you use the "Force > rasterization" option in the print dialog? Yes. Some observations: - What does "force rasterizat

[okular] [Bug 398442] okular doesn't respect page reverse setting of PPD or lpadmin

https://bugs.kde.org/show_bug.cgi?id=398442 --- Comment #9 from Frederick Eaton --- Thanks Michael for clarifying that you can reproduce the bug. > In the end, the processing is done by CUPS (or the CUPS filters > involved) according to the "outputorder" CUPS option. Okular do

[okular] [Bug 398442] okular doesn't respect page reverse setting of PPD or lpadmin

https://bugs.kde.org/show_bug.cgi?id=398442 --- Comment #10 from Frederick Eaton --- Here is where I got the data about ~/.cups/lpoptions: https://askubuntu.com/questions/339607/why-dont-applications-respect-a-printers-default-options -- You are receiving this mail because: You are watching

[okular] [Bug 384695] Configurable horizontal scrolling key (ALT or SHIFT) + WHEEL

https://bugs.kde.org/show_bug.cgi?id=384695 Frederick Eaton changed: What|Removed |Added CC||frede...@ofb.net --- Comment #2 from

[valgrind] [Bug 366035] New: valgrind misses buffer overflow, segfaults in malloc in localtime

https://bugs.kde.org/show_bug.cgi?id=366035 Bug ID: 366035 Summary: valgrind misses buffer overflow, segfaults in malloc in localtime Product: valgrind Version: 3.11.0 Platform: Archlinux Packages OS: Linux

[valgrind] [Bug 366035] valgrind misses buffer overflow, segfaults in malloc in localtime

https://bugs.kde.org/show_bug.cgi?id=366035 --- Comment #1 from Frederick Eaton --- Created attachment 100267 --> https://bugs.kde.org/attachment.cgi?id=100267&action=edit code and output file You are welcome to critique my coding style. -- You are receiving this mail because:

[valgrind] [Bug 366035] valgrind misses buffer overflow, segfaults in malloc in localtime

https://bugs.kde.org/show_bug.cgi?id=366035 --- Comment #2 from Frederick Eaton --- Created attachment 100269 --> https://bugs.kde.org/attachment.cgi?id=100269&action=edit output file only -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 366035] valgrind misses buffer overflow, segfaults in malloc in localtime

https://bugs.kde.org/show_bug.cgi?id=366035 Frederick Eaton changed: What|Removed |Added Attachment #100269|0 |1 is obsolete

[valgrind] [Bug 366035] valgrind misses buffer overflow, segfaults in malloc in localtime

https://bugs.kde.org/show_bug.cgi?id=366035 --- Comment #5 from Frederick Eaton --- Created attachment 100309 --> https://bugs.kde.org/attachment.cgi?id=100309&action=edit verbose output -- You are receiving this mail because: You are watching all bug changes.

[valgrind] [Bug 366035] valgrind misses buffer overflow, segfaults in malloc in localtime

https://bugs.kde.org/show_bug.cgi?id=366035 --- Comment #6 from Frederick Eaton --- Hi Philippe, Thanks for responding. I'm using Arch Linux, it's weird that the default Arch package is not to your liking. Well I compiled from ABS adding (!strip debug) to OPTIONS in /etc/makepkg.con

[valgrind] [Bug 366035] valgrind misses buffer overflow, segfaults in malloc in localtime

https://bugs.kde.org/show_bug.cgi?id=366035 Frederick Eaton changed: What|Removed |Added CC||frede...@ofb.net -- You are receiving this

[valgrind] [Bug 366035] valgrind misses buffer overflow, segfaults in malloc in localtime

https://bugs.kde.org/show_bug.cgi?id=366035 --- Comment #8 from Frederick Eaton --- > Forcing the channel to 1 at that 'BUG' place has other consequences than just > allocating a 'too small' buffer. > As I understand, after this 'forcing to 1', we will als

[valgrind] [Bug 366035] valgrind misses buffer overflow, segfaults in malloc in localtime

https://bugs.kde.org/show_bug.cgi?id=366035 --- Comment #10 from Frederick Eaton --- Hi Philippe, Thanks for the suggestions. I'm afraid I don't have time to fix the full bug, and I think whoever updates syswrap-linux.c will want to have a working version of the bug to experiment wit

[valgrind] [Bug 366035] valgrind misses buffer overflow, segfaults in malloc in localtime

https://bugs.kde.org/show_bug.cgi?id=366035 Frederick Eaton changed: What|Removed |Added Attachment #100267|0 |1 is obsolete

[valgrind] [Bug 366035] valgrind misses buffer overflow, segfaults in malloc in localtime

https://bugs.kde.org/show_bug.cgi?id=366035 --- Comment #14 from Frederick Eaton --- On Arch Linux, I think the only non-obvious packages needed to make the example compile are alsa-lib and libsndfile ... -- You are receiving this mail because: You are watching all bug changes.