[okular] [Bug 500822] Printing an unscaled PDF shifts the contents

2025-02-27 Thread Matthias Urlichs
https://bugs.kde.org/show_bug.cgi?id=500822 --- Comment #2 from Matthias Urlichs --- Created attachment 178953 --> https://bugs.kde.org/attachment.cgi?id=178953&action=edit Image This picture shows the result, including the fact that "lpr" prints the file correctly. --

[okular] [Bug 500822] Printing an unscaled PDF shifts the contents

2025-02-27 Thread Matthias Urlichs
https://bugs.kde.org/show_bug.cgi?id=500822 --- Comment #3 from Matthias Urlichs --- I attached a picture that shows the result, including a correct printout by "lpr -o print-scaling=none". -- You are receiving this mail because: You are watching all bug changes.

[okular] [Bug 500822] Printing an unscaled PDF shifts the contents

2025-02-27 Thread Matthias Urlichs
https://bugs.kde.org/show_bug.cgi?id=500822 Matthias Urlichs changed: What|Removed |Added Platform|Other |Debian testing --- Comment #1 from Matthias

[okular] [Bug 500822] New: Printing an unscaled PDF shifts the contents

2025-02-27 Thread Matthias Urlichs
https://bugs.kde.org/show_bug.cgi?id=500822 Bug ID: 500822 Summary: Printing an unscaled PDF shifts the contents Classification: Applications Product: okular Version: 24.12.2 Platform: Other OS: Linux Status: RE

[kwave] [Bug 445161] New: Kwave eats 100% CPU while recording

2021-11-08 Thread Matthias Urlichs
https://bugs.kde.org/show_bug.cgi?id=445161 Bug ID: 445161 Summary: Kwave eats 100% CPU while recording Product: kwave Version: 21.08.3 Platform: Other OS: Linux Status: REPORTED Severity: normal

[valgrind] [Bug 374940] i386: Stack access at -1(%%esp)

2017-01-23 Thread Matthias Urlichs
https://bugs.kde.org/show_bug.cgi?id=374940 --- Comment #8 from Matthias Urlichs --- (In reply to Julian Seward from comment #6) > Why does libev have to be non-conforming in this way? There are plenty of > other packages that do high-performance thread stuff and I've never heard

[valgrind] [Bug 374940] i386: Stack access at -1(%%esp)

2017-01-22 Thread Matthias Urlichs
https://bugs.kde.org/show_bug.cgi?id=374940 --- Comment #4 from Matthias Urlichs --- Well the libev author thinks that his code works and doesn't break anything … * the value isn't used, thus doesn't matter, thus valgrind has no business complaining. * the kernel needs to handl

[valgrind] [Bug 374940] i386: Stack access at -1(%%esp)

2017-01-12 Thread Matthias Urlichs
https://bugs.kde.org/show_bug.cgi?id=374940 --- Comment #2 from Matthias Urlichs --- It's used as a memory barrier. The Linux kernel uses addl %0,0(%%esp) for the same purpose. I have no idea why libev uses -1 but its author argues that his use of -1 is not wrong and therefore valgrind shou

[valgrind] [Bug 374940] New: i386: Stack access at -1(%%esp)

2017-01-11 Thread Matthias Urlichs
https://bugs.kde.org/show_bug.cgi?id=374940 Bug ID: 374940 Summary: i386: Stack access at -1(%%esp) Product: valgrind Version: 3.12 SVN Platform: Debian testing OS: Linux Status: UNCONFIRMED Severity: norm