[kwin] [Bug 484963] Incorrect client geometry reported via KWin scripting API for gtk4-demo running on XWayland
https://bugs.kde.org/show_bug.cgi?id=484963 Michael Weghorn changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #2 from Michael Weghorn --- After discussion on a similar ticket for GNOME Shell (see https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/7559 ), I think the returned values are fine and my expectations were wrong. -> Closing as INVALID > This is e.g. relevant for accessibility tools. (E.g. a magnifier that > automatically follows the position of the text caret would might then result > in the wrong part of the screen being in view.) > I ran into this while implementing support in Accerciser to retrieve window > coordinates from KWin on Wayland. This works now with an updated MR taking into account the discussion from above-mentioned gnome-shell ticket: https://gitlab.gnome.org/GNOME/accerciser/-/merge_requests/57 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484963] Incorrect client geometry reported via KWin scripting API for gtk4-demo running on XWayland
https://bugs.kde.org/show_bug.cgi?id=484963 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de --- Comment #1 from Michael Weghorn --- Created attachment 168083 --> https://bugs.kde.org/attachment.cgi?id=168083=edit Screenshot showing current result on Fedora Rawhide -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484963] New: Incorrect client geometry reported via KWin scripting API for gtk4-demo running on XWayland
https://bugs.kde.org/show_bug.cgi?id=484963 Bug ID: 484963 Summary: Incorrect client geometry reported via KWin scripting API for gtk4-demo running on XWayland Classification: Plasma Product: kwin Version: 6.0.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: scripting Assignee: kwin-bugs-n...@kde.org Reporter: m.wegh...@posteo.de Target Milestone: --- Created attachment 168082 --> https://bugs.kde.org/attachment.cgi?id=168082=edit Sample KWin script to print client geometry of all windows SUMMARY KWin commit https://invent.kde.org/plasma/kwin/-/commit/51642177e370f4cf902d15494f700c27a9961b9c added a Window.clientGeometry property that can be used to query the client geometry via the KWin scripting API, which is very useful. The client geometry is incorrect however e.g. when querying it for the gtk4-demo app when running it on XWayland in a Plasma Wayland session. STEPS TO REPRODUCE 1. run KDE Plasma Wayland 2. run gtk4-demo as a native Wayland application: gtk4-demo 3. run gtk4-demo on XWayland: GDK_BACKEND=x11 gtk4-demo 4. move both of the gtk4-demo windows to the top edge of the screen (y coordinate 0). 5. load the attached KWin script that prints window information: $ dbus-send --print-reply --dest=org.kde.KWin /Scripting org.kde.kwin.Scripting.loadScript string:$(readlink -f kwin6-print-window-infos.js) method return time=1712133458.716388 sender=:1.20 -> destination=:1.102 serial=2231 reply_serial=2 int32 4 6. run the script loaded in the previous step (adjust script path according to the number in the output from step 5, here it's script number 4). dbus-send --print-reply --dest=org.kde.KWin /Scripting/Script4 org.kde.kwin.Script.run 7. Check the script output in systemd journal: sudo journalctl -e Sample output: Apr 03 10:37:43 fedora kwin_wayland[7262]: js: caption: , bufferGeometry: QRectF(0, 0, 1920, 1080), clientGeometry: QRectF(0, 0, 1920, 1080) Apr 03 10:37:43 fedora kwin_wayland[7262]: js: caption: , bufferGeometry: QRectF(1920, 0, 1920, 1032), clientGeometry: QRectF(1920, 0, 1920, 1032) Apr 03 10:37:43 fedora kwin_wayland[7262]: js: caption: Wayland to X Recording bridge — Xwayland Video Bridge, bufferGeometry: QRectF(-99, 0, 100, 100), clientGeometry: QRectF(-99, 0, 100, 100) Apr 03 10:37:43 fedora kwin_wayland[7262]: js: caption: , bufferGeometry: QRectF(0, 1036, 1920, 60), clientGeometry: QRectF(0, 1036, 1920, 60) Apr 03 10:37:43 fedora kwin_wayland[7262]: js: caption: ~ : bash — Konsole, bufferGeometry: QRectF(0, 28, 958, 1008), clientGeometry: QRectF(0, 28, 958, 1008) Apr 03 10:37:43 fedora kwin_wayland[7262]: js: caption: GTK Demo, bufferGeometry: QRectF(1029, -12, 828, 629), clientGeometry: QRectF(1043, 0, 800, 600) Apr 03 10:37:43 fedora kwin_wayland[7262]: js: caption: GTK Demo <2>, bufferGeometry: QRectF(1028, -12, 828, 629), clientGeometry: QRectF(1028, -12, 828, 629) Apr 03 10:37:43 fedora kwin_wayland[7262]: js: caption: kwin6-print-window-infos.js — Kate, bufferGeometry: QRectF(0, 28, 1920, 1008), clientGeometry: QRectF(0, 28, 1920, 1008) OBSERVED RESULT The client geometry for gtk4-demo running as a native Wayland app is correct: clientGeometry: QRectF(1043, 0, 800, 600) However, the client geometry for gtk4-demo running on XWayland is incorrect: clientGeometry: QRectF(1028, -12, 828, 629) EXPECTED RESULT The client geometry for gtk4-demo running on XWayland should also have a y position of 0. SOFTWARE/OS VERSIONS Fedora Rawhide, up-to-date as of 2024-04-03 Operating System: Fedora Linux 41 KDE Plasma Version: 6.0.3 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.9.0-0.rc1.20240326git928a87efa423.17.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i7-8850H CPU @ 2.60GHz Memory: 15.6 GiB of RAM Graphics Processor: llvmpipe Manufacturer: QEMU Product Name: Standard PC (Q35 + ICH9, 2009) System Version: pc-q35-8.2 $ dnf info kwin-wayland Last metadata expiration check: 0:00:06 ago on Wed 03 Apr 2024 10:48:23 AM CEST. Installed Packages Name : kwin-wayland Version : 6.0.3.1 Release : 2.fc41 Architecture : x86_64 Size : 1.7 M Source : kwin-6.0.3.1-2.fc41.src.rpm Repository : @System >From repo: rawhide Summary : KDE Window Manager with Wayland support URL : https://userbase.kde.org/KWin License : BSD-2-Clause AND BSD-3-Clause AND CC0-1.0 AND GPL-2.0-only AND GPL-2.0-or-later AND GPL-3.0-only AND GPL-3.0-or-later AND LGPL-2.0-only AND LGPL-2.0-or-later AND LGPL-2.1-only AND LGPL-2.1-or-later AND LGPL-3.0-only AND : (GPL-2.0-only OR GPL-3.0-only) AND (LGPL-2.1-only OR LGPL-3.0-only) AND MIT Description : KDE Window Manager with Wayland support. $ dnf info gtk4 Waiting for process with pid
[frameworks-kio] [Bug 483350] Name filters with parenthesis in name are truncated with native KF6 file dialog
https://bugs.kde.org/show_bug.cgi?id=483350
Michael Weghorn changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
||ma/plasma-integration/-/com
||mit/448b8aef5751608e6de05a8
||c31741cea1035dabb
Status|ASSIGNED|RESOLVED
Resolution|--- |FIXED
--- Comment #2 from Michael Weghorn ---
Git commit 448b8aef5751608e6de05a8c31741cea1035dabb by Michael Weghorn.
Committed on 12/03/2024 at 15:13.
Pushed by nicolasfella into branch 'master'.
Don't truncate filter name containing parenthesis
When extracting the part of the string that contains the
filter name, use the part in front of the *last* parenthesis,
not the first one, since otherwise the name gets truncated
if it contains parenthesis itself, e.g. in a call like
QFileDialog dialog;
dialog.setNameFilters({"ODF Spreadsheet (.ods) (*.ods)"});
This is in line with the fact that
`QPlatformFileDialogHelper::cleanFilterList` just considers
those extensions in the last set of parenthesis and aligns
the behavior with the non-native QFileDialog implementation
that the Qt library itself provides, as well as the KF 5
implementation.
M +1-1qt6/src/platformtheme/kdeplatformfiledialoghelper.cpp
https://invent.kde.org/plasma/plasma-integration/-/commit/448b8aef5751608e6de05a8c31741cea1035dabb
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kio] [Bug 481287] Name filters don't work with native KF6 file dialog
https://bugs.kde.org/show_bug.cgi?id=481287 Michael Weghorn changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=483350 --- Comment #18 from Michael Weghorn --- (In reply to Michael Weghorn from comment #17) > I can reproduce the LO scenario after undoing those local changes, so > there's apparently another issue either on LO or on KF6 side. > > I've reopened https://bugs.documentfoundation.org/show_bug.cgi?id=159701 for > now to keep track of this. Looks like another KF6 issue to me, so I've created another bug report + MR with a suggested fix: bug 483350 https://invent.kde.org/plasma/plasma-integration/-/merge_requests/140 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 483350] Name filters with parenthesis in name are truncated with native KF6 file dialog
https://bugs.kde.org/show_bug.cgi?id=483350 Michael Weghorn changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=481287 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 483350] Name filters with parenthesis in name are truncated with native KF6 file dialog
https://bugs.kde.org/show_bug.cgi?id=483350 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 483350] New: Name filters with parenthesis in name are truncated with native KF6 file dialog
https://bugs.kde.org/show_bug.cgi?id=483350 Bug ID: 483350 Summary: Name filters with parenthesis in name are truncated with native KF6 file dialog Classification: Frameworks and Libraries Product: frameworks-kio Version: git master Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Open/save dialogs Assignee: kio-bugs-n...@kde.org Reporter: m.wegh...@posteo.de CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 167044 --> https://bugs.kde.org/attachment.cgi?id=167044=edit Sample program to reproduce the bug SUMMARY QFileDialog allows the use of named filters, e.g. QFileDialog::setNameFilters to set filters and QFileDialog::selectedNameFilter to retrieve the currently selected filter. However, QFileDialog::selectedNameFilter currently doesn't return the full name of the actually selected filter when that one contains text in parenthesis in addition to the file extensions when using the KF6 version. The KF5 one works or non-native Qt one works as expected. STEPS TO REPRODUCE 1. create a dummy file to select: `mkdir dummy.ods` 2. compile attached sample program main.cpp with Qt 6 and run it on KDE Plasma 6 3. select the "ODF Spreadsheet" filter in the file dialog 4. select the dummy file created in step 1 5. click "Open" 6. check the output on stderr OBSERVED RESULT The returned filter lacks the " (.ods") part that was set in parenthesis before using QFileDialog::setNameFilters: > selected filter: "ODF Spreadsheet (*.ods)" EXPECTED RESULT The actually selected filter should be returned including the text in brackets: > selected filter: "ODF Spreadsheet (.ods) (*.ods)" This works as expected when building against Qt 5 instead (so that the KF 5 version is used) or explicitly disabling the use of the native KF 6 implementation by setting the QFileDialog::DontUseNativeDialog option on the dialog (s. line 17 in the sample program, recompile with that line uncommented to make it work). SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.5.0-25-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-8850H CPU @ 2.60GHz Memory: 11,4 GiB of RAM Graphics Processor: llvmpipe Manufacturer: QEMU Product Name: Standard PC (Q35 + ICH9, 2009) System Version: pc-q35-7.2 ADDITIONAL INFORMATION This bug breaks saving files in LibreOffice when using the kf6 integration and was originally reported there: https://bugs.documentfoundation.org/show_bug.cgi?id=159701 This is a follow-up for bug 481287, which solved part of the problem. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 481287] Name filters don't work with native KF6 file dialog
https://bugs.kde.org/show_bug.cgi?id=481287 Michael Weghorn changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #17 from Michael Weghorn --- (In reply to Michael Weghorn from comment #7) > This works fine for me in a KDE Neon unstable VM and a local build of > LibreOffice master (but should presumably be the same with LO 24.2 instead). Sorry, my bad. That local LO build of mine had local changes I had used to track down the issue fixed in the context of this bug report. I can reproduce the LO scenario after undoing those local changes, so there's apparently another issue either on LO or on KF6 side. I've reopened https://bugs.documentfoundation.org/show_bug.cgi?id=159701 for now to keep track of this. Closing the issue here again, as that one *is* fixed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 481287] Name filters don't work with native KF6 file dialog
https://bugs.kde.org/show_bug.cgi?id=481287 --- Comment #13 from Michael Weghorn --- (In reply to Andreas Sturmlechner from comment #12) > This works, but it is testing file open - which works fine in LO calc for me > as well, not save though (currently on 24.2.2.1). It's unclear to me why that should make a difference and saving from LO Calc works OK for me on KDE Neon unstable (see comment 7). How can I reproduce your scenario? Is this just setting up a Gentoo VM, install LO and KDE Plasma 6 and start LO there or are more steps needed? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 481287] Name filters don't work with native KF6 file dialog
https://bugs.kde.org/show_bug.cgi?id=481287 --- Comment #11 from Michael Weghorn --- (In reply to Michael Weghorn from comment #10) > (In reply to ariasuni from comment #8) > This should work to compile the sample program: > > (...) > > If you place this together with the sample program in the same directory, > and run `qmake6` (or whatever the path to your Please ignore that last and incomplete sentence. It doesn't add to the steps already mentioned above it, I just forgot to remove it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 481287] Name filters don't work with native KF6 file dialog
https://bugs.kde.org/show_bug.cgi?id=481287 --- Comment #10 from Michael Weghorn --- (In reply to ariasuni from comment #8) > I can’t compile the sample program to test the result, g++ can’t find > `QApplication`, so I suppose I need more setup. I've added a .pro file for qmake as attachment 166947. This should work to compile the sample program: 1) place the .pro and the C++ file (both attachments from this bug report) into the same directory 2) in terminal, from within the directory containing both files: * run `qmake6` (or whatever the path to the Qt 6 qmake is for your distro) * run `make` 3) run the sample program: `./qfiledialog` If you place this together with the sample program in the same directory, and run `qmake6` (or whatever the path to your -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 481287] Name filters don't work with native KF6 file dialog
https://bugs.kde.org/show_bug.cgi?id=481287 --- Comment #9 from Michael Weghorn --- Created attachment 166947 --> https://bugs.kde.org/attachment.cgi?id=166947=edit qmake .pro project file for the sample program -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 481287] Name filters don't work with native KF6 file dialog
https://bugs.kde.org/show_bug.cgi?id=481287 --- Comment #7 from Michael Weghorn --- (In reply to Andreas Sturmlechner from comment #5) > As mentioned in the linked MR[1] unfortunately this is still not fixed on my > system. > > 1. run localc > 2. Ctrl + Shift + S (or File -> Save As) > 3. (Enter random name) Save > > File dialog reappears every time instead of saving the file. This works fine for me in a KDE Neon unstable VM and a local build of LibreOffice master (but should presumably be the same with LO 24.2 instead). Does the sample program from this bug report work for you? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 481287] Name filters don't work with native KF6 file dialog
https://bugs.kde.org/show_bug.cgi?id=481287 Michael Weghorn changed: What|Removed |Added Status|RESOLVED|VERIFIED --- Comment #4 from Michael Weghorn --- Thanks a lot for the fix! I can confirm that both, the attached sample program and the LibreOffice use case work fine for me on a KDE Neon unstable updated today. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 481287] Name filters don't work with native KF6 file dialog
https://bugs.kde.org/show_bug.cgi?id=481287 Michael Weghorn changed: What|Removed |Added Platform|Other |Neon -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 481287] New: Name filters don't work with native KF6 file dialog
https://bugs.kde.org/show_bug.cgi?id=481287 Bug ID: 481287 Summary: Name filters don't work with native KF6 file dialog Classification: Frameworks and Libraries Product: frameworks-kio Version: git master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Open/save dialogs Assignee: kio-bugs-n...@kde.org Reporter: m.wegh...@posteo.de CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 165804 --> https://bugs.kde.org/attachment.cgi?id=165804=edit Sample program to reproduce the bug SUMMARY QFileDialog allows the use of named filters, e.g. QFileDialog::setNameFilters to set filters and QFileDialog::selectedNameFilter to retrieve the currently selected filter. However, QFileDialog::selectedNameFilter currently always returns an empty string instead of the actually selected filter when using the native implementation on KF6. The KF5 one works as expected. STEPS TO REPRODUCE 1. compile attached sample program main.cpp with Qt 6 and run it on KDE Plasma 6 2. in the native file dialog that shows up, select a file that matches the file pattern (e.g. the file main.cpp itself) 3. click "Open" 4. check the output on stderr OBSERVED RESULT The returned filter is empty: > selected filter: "" EXPECTED RESULT The actually selected filter should be returned: > selected filter: "All C++ files (*.cpp *.cc *.C *.cxx *.c++)" This works as expected when building against Qt 5 instead (so that the KF 5 version is used) or explicitly disabling the use of the native KF 6 implementation by setting the QFileDialog::DontUseNativeDialog option on the dialog (s. line 15 in the sample program, recompile with that line uncommented to make it work). SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 6.0.80 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.1 Kernel Version: 6.5.0-17-generic (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-8850H CPU @ 2.60GHz Memory: 11,4 GiB of RAM Graphics Processor: llvmpipe Manufacturer: QEMU Product Name: Standard PC (Q35 + ICH9, 2009) System Version: pc-q35-7.2 ADDITIONAL INFORMATION This bug breaks saving files in LibreOffice when using the kf6 integration and was originally reported there: https://bugs.documentfoundation.org/show_bug.cgi?id=159701 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 481287] Name filters don't work with native KF6 file dialog
https://bugs.kde.org/show_bug.cgi?id=481287 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 392840] Can't seem to use print() multiple times
https://bugs.kde.org/show_bug.cgi?id=392840 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477069] `print` dbus signal doesn't work
https://bugs.kde.org/show_bug.cgi?id=477069 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445058] kwin interactive console does not work
https://bugs.kde.org/show_bug.cgi?id=445058 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 450123] Please add ability to crop images after scan
https://bugs.kde.org/show_bug.cgi?id=450123 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462574] On Wayland, window's doesn't become active when calling QWidget::activateWindow and QWidget::raise
https://bugs.kde.org/show_bug.cgi?id=462574 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 462574] New: On Wayland, window's doesn't become active when calling QWidget::activateWindow and QWidget::raise
https://bugs.kde.org/show_bug.cgi?id=462574 Bug ID: 462574 Summary: On Wayland, window's doesn't become active when calling QWidget::activateWindow and QWidget::raise Classification: Plasma Product: kwin Version: 5.26.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: m.wegh...@posteo.de Target Milestone: --- Created attachment 154260 --> https://bugs.kde.org/attachment.cgi?id=154260=edit Sample app to reproduce SUMMARY On X11, raising a window can be done by calling QWidget::activateWindow and QWidget::raise. However, that does not have the desired effect in a Plasma Wayland session. STEPS TO REPRODUCE 0. run a KDE Plasma Wayland session 1. compile attached sample program against Qt 6 2. run sample program 3. click the "raise other window button" in window "two" OBSERVED RESULT The window "one" is highlighted in the taskbar, but does not become the active window instead of window "two" EXPECTED RESULT Window "one" should become the active window, as is the case when run on X11. SOFTWARE/OS VERSIONS Debian testing with Qt 6.3.1 Linux/KDE Plasma: Operating System: Debian GNU/Linux KDE Plasma Version: 5.26.3 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.6 Kernel Version: 6.0.0-5-amd64 (64-bit) Graphics Platform: Wayland Processors: 4 × Intel® Core™ i5-5300U CPU @ 2.30GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 5500 Manufacturer: LENOVO Product Name: 20CJS11C00 System Version: ThinkPad T550 ADDITIONAL INFORMATION It works as expected when run with QT_QPA_PLATFORM=xcb, i.e. forcing use of Qt's xcb platform plugin. For Qt 5, this is not expected to work since QWindow::requestActivate isn't handled there on Qt side and I don't know whether the underlying problem(s) is in Qt or KWin or elsewhere. This issue was originally reported against LibreOffice, https://bugs.documentfoundation.org/show_bug.cgi?id=152205#c7 contains some more information on 2 scenarios that fail in different ways and might haver different root causes. (A LibreOffice scenario with gtk3 integration works on GNOME, but not KDE Plasma. The sample Qt app doesn't work in any of them, so there might be different issues.) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 459107] Applications closed in maximized state are then opened as small as possible
https://bugs.kde.org/show_bug.cgi?id=459107 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UPSTREAM --- Comment #11 from Michael Weghorn --- This is a LibreOffice bug, fixed in LibreOffice 7.4.2, s. https://bugs.documentfoundation.org/show_bug.cgi?id=150856 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 354163] kscreen sets incorrect monitor resolution and doesn't allow resolution changes
https://bugs.kde.org/show_bug.cgi?id=354163 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 444526] Resolution of external 4k monitor sometimes changes to FHD
https://bugs.kde.org/show_bug.cgi?id=444526 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385135] Monitor connection names differ across X11 and Wayland, causing multi-monitor containment mappings to break when switching session types
https://bugs.kde.org/show_bug.cgi?id=385135 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kinit] [Bug 436538] kdeinit5: Qt: Session management error: networkIdsList argument is NULL
https://bugs.kde.org/show_bug.cgi?id=436538 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445346] GStreamer with waylandsink in KDE Plasma Wayland session: Video doesn't update (works in GNOME or using Weston)
https://bugs.kde.org/show_bug.cgi?id=445346 --- Comment #5 from Michael Weghorn --- Thanks a lot for the quick fix! (In reply to Michael Weghorn from comment #0) > The actual/original use case where I came across this is LibreOffice, which > also uses "waylandsink" for video Playback in Impress presentations (added > in LibreOffice commit > https://git.libreoffice.org/core/+/ > 9d18bc40416b651340804f44ba5fae65f3bbbcfa%5E%21 for the gtk3 variant; I am > currently looking at this for the qt5/kf5/qt6 variant, since the > "qwidgetvideosink" which is currently used for the qt5/kf5 variants is no > longer under development and will possibly not be ported to Qt 6). When retesting this, it turned out that the sample program as well as the LibreOffice case works now, but only when using the gtk3 variant of LibreOffice, not when using the Qt one, which looks like another issue somewhere in the KDE/Qt stack. I've created follow-up bug 445631 with a new sample program that still has issues, but works in Weston. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445631] GStreamer with waylandsink: No video shown when rendered to child widget in Plasma Wayland session (works in Weston)
https://bugs.kde.org/show_bug.cgi?id=445631 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de --- Comment #1 from Michael Weghorn --- Created attachment 143653 --> https://bugs.kde.org/attachment.cgi?id=143653=edit Screencast demonstrating the issue -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445631] New: GStreamer with waylandsink: No video shown when rendered to child widget in Plasma Wayland session (works in Weston)
https://bugs.kde.org/show_bug.cgi?id=445631 Bug ID: 445631 Summary: GStreamer with waylandsink: No video shown when rendered to child widget in Plasma Wayland session (works in Weston) Product: kwin Version: 5.23.3 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: m.wegh...@posteo.de Target Milestone: --- Created attachment 143652 --> https://bugs.kde.org/attachment.cgi?id=143652=edit Sample program to reproduce the issue SUMMARY When using GStreamer's "waylandsink" to play a video, the video does not show if rendered to a widget that is a child widget when run in a KDE Plasma Wayland session using KWin as Wayland compositor. It works fine when using a nested Weston instead. STEPS TO REPRODUCE 1. make sure that gstreamer-plugins-bad and the GStreamer headers are installed 2. download and extract attached sample program 3. build the program using Qt6 (the program is more broken when using Qt 5; note: include paths might have to be adapted in the .pro file): .../path/to/qt6/qmake make 4. run the sample program ./waylandsink 5. look at the program's window. OBSERVED RESULT The window content is blank, no video is shown. EXPECTED RESULT The GStreamer test video should show up, as is e.g. the case when running the sample program in Weston (screencast will be attached.) SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.23.3 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.0-4-amd64 (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz Memory: 62.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 ADDITIONAL INFORMATION * This still happens with the fix for bug 445346 in place. * The sample program "doesn't work at all" when compiled against Qt 5 instead of Qt 6, no window shows up at all. * I've used a self-compiled qtbase (as of commit 6652bf2353) and qtwayland (as of 6a7b8402) from the Qt 6 "dev" branch. * The video is shown just fine when the widget that the video is rendered to does not have a parent widget (s. commented out code in main.cpp in the sample project). * sample program is based on https://github.com/woutervanh/qt-waylandsink-demo * original/actual use case is making video rendering in LibreOffice Impress work for the qt6 integration when run on Wayland -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445346] GStreamer with waylandsink in KDE Plasma Wayland session: Video doesn't update (works in GNOME or using Weston)
https://bugs.kde.org/show_bug.cgi?id=445346 Michael Weghorn changed: What|Removed |Added Attachment #143459|0 |1 is obsolete|| --- Comment #1 from Michael Weghorn --- Created attachment 143461 --> https://bugs.kde.org/attachment.cgi?id=143461=edit Screencast showing differing behaviour between KWin in a Plasma Wayland session and in Weston This is an updated screencast, now actually running the same command in Weston as well, and showing that glimagesink works: * first shows that waylandsink doesn't work as expected in "default" Plasma Wayland session * then shows that waylandsink works in Weston * then shows that glimagesink works in "default" Plasma Wayland session as well (first version was using wrong command from bash history, sorry for that) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445346] GStreamer with waylandsink in KDE Plasma Wayland session: Video doesn't update (works in GNOME or using Weston)
https://bugs.kde.org/show_bug.cgi?id=445346 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 445346] New: GStreamer with waylandsink in KDE Plasma Wayland session: Video doesn't update (works in GNOME or using Weston)
https://bugs.kde.org/show_bug.cgi?id=445346 Bug ID: 445346 Summary: GStreamer with waylandsink in KDE Plasma Wayland session: Video doesn't update (works in GNOME or using Weston) Product: kwin Version: 5.23.2 Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: m.wegh...@posteo.de Target Milestone: --- Created attachment 143459 --> https://bugs.kde.org/attachment.cgi?id=143459=edit Screencast showing the differing behaviour between KWin in a Plasma Wayland session and in Weston SUMMARY When using GStreamer's "waylandsink" to play a video, the video does not update when run in a KDE Plasma Wayland session using KWin as Wayland compositor. It works fine in a GNOME session or when using a nested Weston instead. (Audio is updated just fine, but the image seems "frozen"/stuck.) STEPS TO REPRODUCE 1. make sure that gstreamer-plugins bad and the gst-launch-1.0 command are available * e.g. in Debian testing, packages "gstreamer1.0-tools" and "gstreamer1.0-plugins-bad" need to be installed 2. in a Plasma Wayland session, run this command: gst-launch-1.0 -v videotestsrc ! waylandsink 3. look at the video that is shown OBSERVED RESULT A test video shows up, but it looks like a static image, there are no visible updates. EXPECTED RESULT The rectangle at the bottom right should update, the "black and white dots" should be moving. SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.23.2 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.14.0-2-amd64 (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz Memory: 62.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 ADDITIONAL INFORMATION The expected behaviour can be seen e.g. by: * running the same command inside Weston instead (screencast which shows both, KWin and Weston behaviour is attached) * using "glimagesink" instead of "waylandsink", by running this command: gst-launch-1.0 videotestsrc ! glimagesink. The actual/original use case where I came across this is LibreOffice, which also uses "waylandsink" for video Playback in Impress presentations (added in LibreOffice commit https://git.libreoffice.org/core/+/9d18bc40416b651340804f44ba5fae65f3bbbcfa%5E%21 for the gtk3 variant; I am currently looking at this for the qt5/kf5/qt6 variant, since the "qwidgetvideosink" which is currently used for the qt5/kf5 variants is no longer under development and will possibly not be ported to Qt 6). -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443787] Multimonitor Telegram click on video/picture opens on other screen flickers wildly
https://bugs.kde.org/show_bug.cgi?id=443787 Michael Weghorn changed: What|Removed |Added CC||axel.br...@gmx.de --- Comment #22 from Michael Weghorn --- *** Bug 444026 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 444026] LO Presentation mode broken after update to Plasma 5.23.0
https://bugs.kde.org/show_bug.cgi?id=444026 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de Status|NEEDSINFO |RESOLVED Resolution|UPSTREAM|DUPLICATE --- Comment #6 from Michael Weghorn --- (In reply to David Edmundson from comment #4) > Thanks, please do reopen and comment if anything happens on that libreoffice > bug report that pushes things back our way. FWIW, it turned out this is not a LibreOffice problem, but a KWin regression, already fixed in the 'Plasma/5.23' branch by the following commit: commit 2958881264caf8d3bd83a34411e9586f8fcb7211 Author: Vlad Zahorodnii Date: Fri Oct 15 17:18:43 2021 +0300 Restore old behavior of Workspace::clientArea(clientOpt, Toplevel) When geometry updates are blocked, the output doesn't get updated. This breaks Workspace::clientArea() overload that takes only the window. Previously, clientArea() would look up the output where the window is every time it's called, so the fact that the screen id or AbstractOutput is unsynchronized with the frame geometry was irrelevant. This change restores the old behavior as 5.23 is affected by the output() being out of sync with the frameGeometry(). Specifically, when kwin starts managing an X11 window, it will block geometry updates, setup the window, e.g. make it fullscreen, and unblock geometry updates. Since Workspace::clientArea(clientArea, Toplevel) uses the output(), X11Client::setFullScreen() will most likely put the X11 window at a wrong output if it's called inside X11Client::manage(). BUG: 443787 (cherry picked from commit 6d5fc9fd3000cf32ecb63a8252a6f50368f3604d) src/workspace.cpp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) Marking as a duplicate of bug 443787 accordingly. *** This bug has been marked as a duplicate of bug 443787 *** -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 406464] Unexpected folder selection in native QFileDialog
https://bugs.kde.org/show_bug.cgi?id=406464 Michael Weghorn changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |WORKSFORME --- Comment #3 from Michael Weghorn --- This works as expected now after upgrading from Debian bullseye to bookworm (current testing) which also has newer versions of the Plasma/kf5 packages, e.g. * plasma-integration/testing,now 5.21.5-2 * libkf5kiocore5/testing,now 5.83.0-2 -> closing as WORKSFORME (This may or may not be related to the fix for bug 419874, I didn't take a closer look.) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 432395] Missing border of comboboxes in LO and spinboxes in spectacle
https://bugs.kde.org/show_bug.cgi?id=432395 --- Comment #5 from Michael Weghorn --- (In reply to Fabian Vogt from comment #1) > The issue is that Style::drawFrameLineEditPrimitive runs into the "not > enough room" case. Instead of not drawing the double frame, it decides not > to draw any frame at all. > > The LO issue can be explained by LO not taking frame margins into account > (confirmed by adding 10px, but LO looked the same), so this might be fixed > by > https://github.com/LibreOffice/core/commit/ > 771f1411c588a02ed276febc9a479323bf4232cd. I'm using 7.0.3.1 here, not sure > whether that commit is included. Adding Michael Weghorn for info. That commit (and the others in the series) are only contained from LO 7.1 on, but they do not fix the issue described here (which is still reproducible with LO from git master). I've created https://bugs.documentfoundation.org/show_bug.cgi?id=140088 to keep track of this on LO side. -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 431628] partitionmanager does not wipe old signatures when creating a new partition table
https://bugs.kde.org/show_bug.cgi?id=431628 Michael Weghorn changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED Latest Commit||813e574001eb5b9248c92d2c8c0 ||174d5dd062a26 Version Fixed In||21.04.0 --- Comment #2 from Michael Weghorn --- (In reply to Michael Weghorn from comment #1) > MR with suggested fix: > https://invent.kde.org/system/kpmcore/-/merge_requests/25 The MR was merged now. -> fixed in https://invent.kde.org/system/kpmcore/-/commit/813e574001eb5b9248c92d2c8c0174d5dd062a26 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 431628] partitionmanager does not wipe old signatures when creating a new partition table
https://bugs.kde.org/show_bug.cgi?id=431628 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de --- Comment #1 from Michael Weghorn --- While sfdisk automatically wipes old signatures in interactive mode, it does not do so in non-interactive mode. When run in interactive mode, i.e. from a terminal, sfdisk shows this warning: $ sudo sfdisk /dev/sda [...] The device contains 'iso9660' signature and it will be removed by a write command. See sfdisk(8) man page and --wipe option for more details. [...] However, when explicitly disabling wiping (or running in non-interactive mode, as partitionmanager does), this warning is shown $ sudo sfdisk --wipe=never /dev/sda [] The device contains 'iso9660' signature and it may remain on the device. It is recommended to wipe the device with wipefs(8) or sfdisk --wipe, in order to avoid possible collisions. [...] and signatures are not wiped. MR with suggested fix: https://invent.kde.org/system/kpmcore/-/merge_requests/25 -- You are receiving this mail because: You are watching all bug changes.
[partitionmanager] [Bug 431628] New: partitionmanager does not wipe old signatures when creating a new partition table
https://bugs.kde.org/show_bug.cgi?id=431628 Bug ID: 431628 Summary: partitionmanager does not wipe old signatures when creating a new partition table Product: partitionmanager Version: Git Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: andr...@stikonas.eu Reporter: m.wegh...@posteo.de Target Milestone: --- SUMMARY partitionmanager does not wipe old signatures when creating partition table. STEPS TO REPRODUCE 1. insert USB drive 2. download a CD ISO image, e.g. https://cdimage.debian.org/debian-cd/current/amd64/iso-cd/debian-10.7.0-amd64-netinst.iso 2. copy the image to the USB drive using dd, command if USB drive is /dev/sda: sudo dd if=/path/to/debian-10.7.0-amd64-netinst.iso of=/dev/sda 3. in partitionmanager, create a new partition table for the USB device 3.1. right-click on the USB device 3.2. select -> "New Partition Table" 3.3. leave default selection "GPT" and click "Create New Partition Table" 3.4. click the "Apply" button, and "Apply Pending Operations" 4. check signatures on the device, e.g. run 'sudo file -s /dev/sda' OBSERVED RESULT output is: $ sudo file -s /dev/sda /dev/sda: ISO 9660 CD-ROM filesystem data (DOS/MBR boot sector) 'Debian 10.7.0 amd64 n' (bootable) EXPECTED RESULT There should be no more "iso9660" signature after a new partition table has been created. The output should be something like: $ sudo file -s /dev/sda /dev/sda: DOS/MBR boot sector; partition 1 : ID=0xee, start-CHS (0x0,0,2), end-CHS (0x3ff,255,63), startsector 1, 15633407 sectors, extended partition table (last) SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.77.0 Qt Version: 5.15.2 Kernel Version: 5.10.0-1-amd64 OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz Memory: 62.4 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 630 ADDITIONAL INFORMATION * Not wiping the signatures also leads to the device's partitions not properly being shown in gparted after taking the above steps + creating partitions in partitionmanager, then starting gparted (e.g. an actual FAT32 partition is shown as having file system "iso9660" instead). * Reproducible using kpmcore master as of commit 31706cffdc1df60b96010fbbdbbdc6ec192fd913 and partitionmanager as of commit 42c46fa67425c3bffb864a1056e56688e2fd3784. * I have investigated this and plan to submit a MR for kpmcore that fixes this bug. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430376] QWidget doesn't correctly open in full screen on specific monitor if told to do so on Wayland
https://bugs.kde.org/show_bug.cgi?id=430376 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 430376] New: QWidget doesn't correctly open in full screen on specific monitor if told to do so on Wayland
https://bugs.kde.org/show_bug.cgi?id=430376
Bug ID: 430376
Summary: QWidget doesn't correctly open in full screen on
specific monitor if told to do so on Wayland
Product: kwin
Version: 5.19.5
Platform: Debian testing
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: wayland-generic
Assignee: kwin-bugs-n...@kde.org
Reporter: m.wegh...@posteo.de
Target Milestone: ---
Created attachment 134071
--> https://bugs.kde.org/attachment.cgi?id=134071=edit
Sample program to reproduce the issue
SUMMARY
In a dual screen setup, trying to open a QWidget in full screen on a specific
monitor does not work on Wayland, which breaks e.g. LibreOffice Impress
presentation mode.
STEPS TO REPRODUCE
0. use KDE Plasma Wayland with a dual screen setup
1. compile and run the attached sample program "main.cpp" (source code also
given below)
2. run the program
OBSERVED RESULT
Two white/empty widgets open in full screen on the first/same screen.
EXPECTED RESULT
One full screen widget on each of the two screens.
SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.19.5
KDE Frameworks Version: 5.74.0
Qt Version: 5.15.1
Kernel Version: 5.9.0-4-amd64
OS Type: 64-bit
Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz
Memory: 62.4 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 630
ADDITIONAL INFORMATION
* It works as expected when run with env variable 'QT_QPA_PLATFORM=xcb' set,
i.e. using XWayland.
* My setup for testing includes a laptop with an internal screen + an attached
external screen, both with a resolution of 1920x1080.
* This was originally reported as a LibreOffice Impress bug at
https://bugs.documentfoundation.org/show_bug.cgi?id=128214
* The LibreOffice scenario works fine when using LibreOffice with the gtk3
integration ("VCL plugin") on GNOME Wayland, but not when using the gtk3
integration on Plasma Wayland either (tested with LibreOffice from Debian
testing, package version 7.0.3-4+b1).
* Sample program:
#include
#include
#include
#include
int main(int argc, char *argv[])
{
QApplication a(argc, argv);
for (QScreen* screen : qApp->screens()) {
QWidget * widget = new QWidget;
widget->show();
QRect screenGeometry = screen->geometry();
widget->windowHandle()->setScreen(screen);
widget->move(screenGeometry.topLeft());
widget->showFullScreen();
}
return a.exec();
}
--
You are receiving this mail because:
You are watching all bug changes.
[frameworks-kwayland] [Bug 408358] Use after free in KDE Wayland integration
https://bugs.kde.org/show_bug.cgi?id=408358 Michael Weghorn changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED --- Comment #2 from Michael Weghorn --- I can't reproduce this anymore with Plasma 5.19.5 on a current Debian testing (with libwayland-client0 1.18.0-2~exp1.1, plasma-integration 5.19.5-3). -> Closing as WORKSFORME (In reply to David Edmundson from comment #1) > [18:21] you don't want to create a second XdgShellSurface, Qt has one > internally > [18:25] it's a protocol violation so a correct compositor should kick > out the client > [18:26] unfortunately Qt's XdgShellTopLevel object is not exposed > anywhere > > > That needs a patch in Qt at which point we may as well support setAppId > explicitly there. > > Will leave this open to remind us to fix. @David: I don't immediately see how this is related to the issue originally reported here - to me, this comment sounds more related to https://bugreports.qt.io/browse/QTBUG-77182 (Qt: "Export Wayland xdg_toplevel app ID to allow changing the icon of a Window") and https://bugs.documentfoundation.org/show_bug.cgi?id=125934 (LibreOffice: "No application icon on Wayland with the qt5 / kf5 backend") , respectively... -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 428973] Border one pixel off when drawing 'QStyle::PE_Frame' primitive using Breeze style
https://bugs.kde.org/show_bug.cgi?id=428973
Michael Weghorn changed:
What|Removed |Added
Latest Commit||https://invent.kde.org/plas
||ma/breeze/commit/7e678c344b
||3d931acafe495a1e19d23199aac
||ca7
Status|REPORTED|RESOLVED
Resolution|--- |FIXED
--- Comment #4 from Michael Weghorn ---
Git commit 7e678c344b3d931acafe495a1e19d23199aacca7 by Michael Weghorn.
Committed on 11/11/2020 at 13:09.
Pushed by ngraham into branch 'master'.
Draw frame outline at the outer edge, not a pixel further inside
The documentation for 'QPainter::drawRoundedRect' [1]
says:
"A filled rectangle has a size of rect.size(). A stroked
rectangle has a size of rect.size() plus the pen width."
Therefore, the frame rect passed to that method needs to
be adjusted according to the pen width for the case where
the rect is stroked (i.e. an outline exists), and no
adjustement is needed when the rect is not stroked so
that
[size of rect] + [outline width] = [wanted total size]
The default pen size is 1 (which is also the value
of 'PenWidth::Frame' used to calculate the radius for the
outline a few lines further down).
For the case that an outline exists, the adjustment of
the rect already happens in the call to 'Helper::strokedRect',
so there is no need for reducing the rect by one additional
pixel on each side, which resulted in the frame border
unnecessarily not being right at the inner edge of the
rect, but one additional pixel "further inside".
It looks like the additional adjustment was originally added
by commit 3dbcea7e59cba2ae3afa1a66234502afa7d476d1
("Changed frame width to 2, to cope with focus rect.",
2014-07-30), later adapted by commit
f288c34c3e0f16217538453620f94fb637a20d6c
("Render 2px focused outline *inside* frames rather than outside",
2014-08-11) and commit 2985b4cb6b036a3fcbea6ba6c9fc79eb90f528dc
("use one pixel for focus frame instead of 2", 2014-09-22).
While 'Metrics::Frame_FrameWidth' still has the value 2,
it is not used here at all, so the default pen width of 1
applies.
Therefore, drop the extra adjustment in order for the
stroke to be drawn right at the edge of the rect.
[1] https://doc.qt.io/qt-5/qpainter.html#drawRoundedRect
M +1-1kstyle/breezehelper.cpp
https://invent.kde.org/plasma/breeze/commit/7e678c344b3d931acafe495a1e19d23199aacca7
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 428973] Border one pixel off when drawing 'QStyle::PE_Frame' primitive using Breeze style
https://bugs.kde.org/show_bug.cgi?id=428973 --- Comment #3 from Michael Weghorn --- (In reply to Michael Weghorn from comment #0) > From my analysis, > it's a bug in the Breeze theme, I plan to submit a merge request to fix this > soon. -> https://invent.kde.org/plasma/breeze/-/merge_requests/51 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 428973] Border one pixel off when drawing 'QStyle::PE_Frame' primitive using Breeze style
https://bugs.kde.org/show_bug.cgi?id=428973 --- Comment #2 from Michael Weghorn --- Created attachment 133232 --> https://bugs.kde.org/attachment.cgi?id=133232=edit Screenshot of enlarged image (where exact pixels can be seen more easily) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 428973] Border one pixel off when drawing 'QStyle::PE_Frame' primitive using Breeze style
https://bugs.kde.org/show_bug.cgi?id=428973 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de --- Comment #1 from Michael Weghorn --- Created attachment 133231 --> https://bugs.kde.org/attachment.cgi?id=133231=edit Image created by running the sample program -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 428973] New: Border one pixel off when drawing 'QStyle::PE_Frame' primitive using Breeze style
https://bugs.kde.org/show_bug.cgi?id=428973 Bug ID: 428973 Summary: Border one pixel off when drawing 'QStyle::PE_Frame' primitive using Breeze style Product: Breeze Version: 5.17.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: QStyle Assignee: unassigned-b...@kde.org Reporter: m.wegh...@posteo.de Target Milestone: --- Created attachment 133230 --> https://bugs.kde.org/attachment.cgi?id=133230=edit Small sample program SUMMARY When drawing a frame border/outline using QApplication::style()->drawPrimitive(QStyle::PE_Frame,...) with the Breeze style, the border is not drawn at the outer edge of the rectangle being passed, but an additional pixel "too far inside" of the rectangle. This e.g. leads to borders not being shown correctly when LibreOffice is used with the qt5/kf5 integration (s. details below.) STEPS TO REPRODUCE 1. Compile attached sample program "main.cpp" 2. run it (it creates an image file in /tmp/frame.png) 3. open the file /tmp/frame.png and check the position and total size of the rectangle, including the border OBSERVED RESULT * The rectangle border starts at pixel (6,6). * The rectangle (including the border) has a width and height of 8 pixels. EXPECTED RESULT Since the rect that was specified in the option as a 'QRect(5, 5, 10, 10)': * The rectangle border should start at pixel (5,5). * The rectangle (including the border) should have a width of and height of 10 pixels SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 Kernel Version: 5.9.0-1-amd64 OS Type: 64-bit Processors: 12 × Intel® Core™ i7-9850H CPU @ 2.60GHz Memory: 62.4 GiB of RAM ADDITIONAL INFORMATION * The border is placed as expected when using the Fusion style instead (e.g. by setting env variable QT_STYLE_OVERRIDE=Fusion). * The border is placed as expected when using a QStyle::PE_FrameWindow primitive instead of QStyle::PE_Frame. * Tested with Breeze style 5.17.5 from Debian packages as well as current git master (as of c06b43dc99d68543f6f100517883620f60028f9c). * This bug report is based on LibreOffice bug reports https://bugs.documentfoundation.org/show_bug.cgi?id=138010 and https://bugs.documentfoundation.org/show_bug.cgi?id=137956. The issue described here leads to various borders not being shown when LibreOffice is used with the qt5/kf5 integration and the Breeze style. From my analysis, it's a bug in the Breeze theme, I plan to submit a merge request to fix this soon. -- You are receiving this mail because: You are watching all bug changes.
[flatpak-platform-plugin] [Bug 427295] crash in qxdgdesktopportalfiledialog with krita 4.4 beta
https://bugs.kde.org/show_bug.cgi?id=427295 --- Comment #6 from Michael Weghorn --- (In reply to Jan Grulich from comment #5) > It no longer crashes with the updated runtime, however there is still this > issue that the saving dialog freezes whole application upon confirmation. Is this also related to https://codereview.qt-project.org/c/qt/qtbase/+/308145 or a different issue? -- You are receiving this mail because: You are watching all bug changes.
[flatpak-platform-plugin] [Bug 427295] crash in qxdgdesktopportalfiledialog with krita 4.4 beta
https://bugs.kde.org/show_bug.cgi?id=427295 --- Comment #3 from Michael Weghorn --- Thankfully, Giuseppe D'Angelo has already submitted a patch to Qt's Gerrit: https://codereview.qt-project.org/c/qt/qtbase/+/316248 -- You are receiving this mail because: You are watching all bug changes.
[flatpak-platform-plugin] [Bug 427295] crash in qxdgdesktopportalfiledialog with krita 4.4 beta
https://bugs.kde.org/show_bug.cgi?id=427295 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de --- Comment #2 from Michael Weghorn --- (In reply to Jan Grulich from comment #1) > Looks like a recent change in Qt is causing this crash: > https://codereview.qt-project.org/c/qt/qtbase/+/308145 > > I notified the author of the change and if he doesn't respond, I will try to > investigate or temporarily revert it. Probably the same issue as reported in https://bugreports.qt.io/browse/QTBUG-87143, which includes a small sample program . I hope I'll be able to take a look today or tomorrow. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424937] Okular sends blank pages do printer
https://bugs.kde.org/show_bug.cgi?id=424937 --- Comment #10 from Michael Weghorn --- (In reply to Michael from comment #9) > don't forget when I print the same file from another PDF viewer it is > printing right, I guess that means the problem isn't in the printer or > somewhere else right? Not necessarily. Other PDF viewers often hand over PDF to CUPS for printing, so the processing inside CUPS (the CUPS filter chain) is different as for the case where PostScript is passed, which Okular does by default. Therefore, issues that only happen inside the printing system may not be exposed by using other viewers. When using rasterized printing, Okular also passes PDF, so that's usually a rather good indicator (though other aspects than just the file format itself may expose bugs in the printer or printing system as well), as is the fact whether printing the PostScript file manually works. (If printing manually from command line shows the same problem, the issue is probably outside of Okular.) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 424937] Okular sends blank pages do printer
https://bugs.kde.org/show_bug.cgi?id=424937 Michael Weghorn changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #8 from Michael Weghorn --- (In reply to Michael from comment #6) > Created attachment 131628 [details] > ps file > The file itself looks OK and is not blank, so it might be that the issue is outside of Okular's control, somewhere in the printing system or the printer itself. Does it work if you print that file directly from command line like this (run it in the directory where the file is located): lp -d d00028-001 > here is a ps file, for the raster test I need some more day because my > printer is in maintenance changing the scanner lamp Whether rasterized printing works would be interesting to know, since this sometimes helps as a workaround for issues with the printing system. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425289] Printing problem: 2 copies on a double sided printer
https://bugs.kde.org/show_bug.cgi?id=425289 --- Comment #6 from Michael Weghorn --- (In reply to Axel Braun from comment #5) > (In reply to Michael Weghorn from comment #4) > > Looking at the PPD: > > > > There's this line in there: > > > *cupsManualCopies: false > > > > What you can *try* is changing that to > > > > > *cupsManualCopies: true > > > > and see whether it helps. > > Unfortunately no :( > > With 'upstream' you probably mean its a CUPS issue? Either CUPS, one of the CUPS filters (which may come from several projects, in your case it might also be the (proprietary?) brother_lpdwrapper_mfc9340cdw filter) or your printer firmware. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425289] Printing problem: 2 copies on a double sided printer
https://bugs.kde.org/show_bug.cgi?id=425289 --- Comment #4 from Michael Weghorn --- Looking at the PPD: There's this line in there: > *cupsManualCopies: false What you can *try* is changing that to > *cupsManualCopies: true and see whether it helps. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425289] Printing problem: 2 copies on a double sided printer
https://bugs.kde.org/show_bug.cgi?id=425289 Michael Weghorn changed: What|Removed |Added Resolution|WAITINGFORINFO |UPSTREAM Status|NEEDSINFO |RESOLVED --- Comment #3 from Michael Weghorn --- (In reply to Axel Braun from comment #2) > Created attachment 131556 [details] > PPD of printer used > > Printer is a Brother MFC 9340 CDW > > Same issue appears if I print the ghostscript file with lp as suggested > (produced by poppler 0.90) Then it's an issue with either the printer or the printing system. Not much we can do on Okular side. As a side note, I've previously seen a similar problem with some Ricoh multi-function device. That one had an option to "optimize empty pages away" in its settings, and disabling that made things work as expected. However, that might not be the same for your printer. > > 'Force Rasterisation' creates indeed 2 copies! At least there's a workaround then... -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415986] Printing to HP1120C with gutenprint driver from Okular not working.
https://bugs.kde.org/show_bug.cgi?id=415986 Michael Weghorn changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #19 from Michael Weghorn --- (In reply to bruce.samha...@samhaber.ca from comment #13) > Created attachment 129749 [details] > Today's /var/log/cups/error_log file > > This is the "/var/log/cups/error_log" file from the 2 printouts today. [...] Unfortunately, this seems to have been created using log level "warning". Can you set CUPS's log level to "Debug" in /etc/cups/cupsd.conf, restart CUPS, try again and attach an updated log? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985
Michael Weghorn changed:
What|Removed |Added
Status|REPORTED|NEEDSINFO
Resolution|--- |WAITINGFORINFO
--- Comment #53 from Michael Weghorn ---
(In reply to bruce.samha...@samhaber.ca from comment #51)
> This is the "/var/log/cups/error_log" file from the 2 printouts today. The
> last printout was a test to print without settin the 'Option: Force
> Rasterization' which generated the arror message as mentioned in previous
> comments. The previous 2 printouts are the US Letter 8.5x11" and the 11x17"
> . Both printouts for the 2 sizes of PDFs are shrinking the image to fit the
> sheet of paper but the last 0.25" or so of the image is not printed, which
> is probably the printer limit. This means the border settings need to be
> adjusted. In the case of the 11x17" paper the printer prints to most of the
> PDF information croping some at the end 14mm (9/16"); the printed image size
> is 413mm x 254mm. In the case of the Letter 8.5x11" paper the printer stops
> printing 16mm (5/8") from the end of the paper, which is a printer
> limitation; the printed image size is 261mm x 191mm.
Hm, unfortunately that log only contains entries for the failed last print job
("Job 655"), none for the actually interesting print job that was probably "Job
654"...
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 396880] Presentation mode in wayland shows panel, obscuring part of the document
https://bugs.kde.org/show_bug.cgi?id=396880 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Michael Weghorn --- Works for me now on Debian testing, seems to have been fixed somewhere outside of Okular itself, s. bug 396879. *** This bug has been marked as a duplicate of bug 396879 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396879] Full screen mode doesn't work in wayland
https://bugs.kde.org/show_bug.cgi?id=396879 --- Comment #4 from Michael Weghorn --- *** Bug 396880 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396879] Full screen mode doesn't work in wayland
https://bugs.kde.org/show_bug.cgi?id=396879
Michael Weghorn changed:
What|Removed |Added
Resolution|--- |WORKSFORME
Status|REPORTED|RESOLVED
--- Comment #3 from Michael Weghorn ---
(In reply to Patrick Silva from comment #2)
> Full screen mode works as expected on my wayland session.
Works on my Debian testing as well now, while it did not in the past. The same
is true for LibreOffice Impress with the kf5 integration ("VCL plugin"), so
this actually seems to have been fixed somewhere in the Qt/kf5 libs.
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.17.5
KDE Frameworks Version: 5.70.0
Qt Version: 5.14.2
Kernel Version: 5.7.0-3-amd64
OS Type: 64-bit
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 424937] Okular sends blank pages do printer
https://bugs.kde.org/show_bug.cgi?id=424937 Michael Weghorn changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||m.wegh...@posteo.de --- Comment #5 from Michael Weghorn --- 2 questions: 1) Can you attach the PostScript file that Okular generates and hands over to CUPS? It's stored a /var/spool/cups/d-001? (If that one is blank, Okular/Poppler probably does something strange, otherwise it's probably not their fault.) 2) Does enabling "Force rasterization" in the "PDF options" tab in the print dialog help? (potential workaround) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 425289] Printing problem: 2 copies on a double sided printer
https://bugs.kde.org/show_bug.cgi?id=425289 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Michael Weghorn --- (In reply to Axel Braun from comment #0) > My feeling is we need to trigger 2 separate print jobs, can this be? This shouldn't be necessary and is generally not a good idea. E.g. if the printer requests to type a PIN when printing (a feature called "confidential printing") or is used by multiple users in parallel and has some functionality to keep printouts of the same print job "in order", that will break (or require to type the PIN/password multiple times). Your issue is most probably one of the printer/printing system. Some questions/thoughts: 1) What printer is this? Can you attach the printer's PPD file (located at /etc/cups/ppd/? 2) Can you try whether you have the same issue when printing the PostScript file generated by Okular from command line? It's located in /var/spool/cups/d-001 and you can print it using lp -n2 -d 3) Does anything change if you check the "Force rasterization" checkbox in the "PDF options" tab of the print dialog? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 414546] [wayland] Accessibility settings do not appear when using wayland
https://bugs.kde.org/show_bug.cgi?id=414546 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 422340] Portal FileChooser incorrectly handles mnemonics
https://bugs.kde.org/show_bug.cgi?id=422340
Michael Weghorn changed:
What|Removed |Added
Status|REPORTED|RESOLVED
Latest Commit||https://invent.kde.org/plas
||ma/xdg-desktop-portal-kde/c
||ommit/daab5c525e7aa14fbd63f
||678adc5f900e627a839
Resolution|--- |FIXED
--- Comment #5 from Michael Weghorn ---
Git commit daab5c525e7aa14fbd63f678adc5f900e627a839 by Michael Weghorn.
Committed on 25/07/2020 at 20:15.
Pushed by grulich into branch 'master'.
FileChooser: Properly handle mnemonics in 'accept_label'
The FileChooser portal doc [1] for 'accept_label' says:
> accept_label s
>
> The label for the accept button. Mnemonic underlines are allowed.
Since Qt does not use underscores/underlines, but the ampersand
character ('&') for mnemonics, convert the retrieved
text accordingly, to make the mnemonic applied at the correct
position and preserve literal '&'s.
[1]
https://flatpak.github.io/xdg-desktop-portal/portal-docs.html#gdbus-org.freedesktop.impl.portal.FileChooser
M +18 -8src/filechooser.cpp
M +2-0src/filechooser.h
https://invent.kde.org/plasma/xdg-desktop-portal-kde/commit/daab5c525e7aa14fbd63f678adc5f900e627a839
--
You are receiving this mail because:
You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 422340] Portal FileChooser incorrectly handles mnemonics
https://bugs.kde.org/show_bug.cgi?id=422340 --- Comment #4 from Michael Weghorn --- (In reply to Jan Grulich from comment #3) > Do you plan to submit your change now? Yes; thanks for all the reviews. I've submitted an MR now: https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/7 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 423694] Prints the square of the quantity requested: ask for 2,get 4; ask for 3, get 9, ask for 4,get 16 sheets.
https://bugs.kde.org/show_bug.cgi?id=423694 Michael Weghorn changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||m.wegh...@posteo.de --- Comment #2 from Michael Weghorn --- What happens if you print from command line instead of using Okular? Please try what happens in these two cases: 1) Printing the original document, command (put actual printer name and name of document accordingly): lp -d 2) Printing the PostScript file that was generated by Okular. That one should be in /var/spool/cups/d-001 Please ask if more details are needed. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 422866] In GtkAssistant's left sidebar, normal text is overlapped by black foreground
https://bugs.kde.org/show_bug.cgi?id=422866
--- Comment #7 from Michael Weghorn ---
(In reply to Michael Weghorn from comment #5)
> Created attachment 129666 [details]
> [...]
> (Not sure whether the fact that the unused part of the sidebar is still
> black is another issue, IMHO this at least looks a bit weird...)
This seems to come from those lines just a few lines above, also can be seen in
Ilhan's comment 4:
> assistant .sidebar {
> background-color: @theme_fg_color;
or, as it is in current master (with "@theme_text_color" instead of
"theme_fg_color"):
https://invent.kde.org/plasma/breeze-gtk/-/blob/84530aee0955d5bfb561ae6267c847cd544d6084/src/gtk3/widgets/_base.scss#L203
Maybe that's intended, to have a certain contrast? I'm not a designer, and
don't know much about the topic...
--
You are receiving this mail because:
You are watching all bug changes.
[Breeze] [Bug 422866] In GtkAssistant's left sidebar, normal text is overlapped by black foreground
https://bugs.kde.org/show_bug.cgi?id=422866 --- Comment #6 from Michael Weghorn --- Created attachment 129667 --> https://bugs.kde.org/attachment.cgi?id=129667=edit Screenshot LibreOffice-internal mail merge wizard (with modification from comment 4) (This is with breeze-gtk-theme 5.17.5-2 from Debian testing and the modification mentioned in comment 4 manually applied.) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 422866] In GtkAssistant's left sidebar, normal text is overlapped by black foreground
https://bugs.kde.org/show_bug.cgi?id=422866 --- Comment #5 from Michael Weghorn --- Created attachment 129666 --> https://bugs.kde.org/attachment.cgi?id=129666=edit Screenshot LibreOffice-internal mail merge wizard (before) The same can be seen with LibreOffice's own mail merge dialog when using the gtk3 VCL plugin: * start LibreOffice Writer, using gtk3 VCL plugin: SAL_USE_VCLPLUGIN=gtk3 libreoffice --writer * start mail merge dialog via "Tools" -> "Mail Merge Wizard" Attached the screenshot without the extra line. I can confirm that adding the line as mentioned in comment 4 makes the non-active entries visible like in Ilhan's example. (Not sure whether the fact that the unused part of the sidebar is still black is another issue, IMHO this at least looks a bit weird...) -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 422866] In GtkAssistant's left sidebar, normal text is overlapped by black foreground
https://bugs.kde.org/show_bug.cgi?id=422866 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422690] Margins often cut when printing (2020 - Okular-1.10.0)
https://bugs.kde.org/show_bug.cgi?id=422690 Michael Weghorn changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |UPSTREAM --- Comment #7 from Michael Weghorn --- (In reply to kolAflash from comment #6) > Opened an issue for CUPS. > https://github.com/OpenPrinting/cups-filters/issues/250 > I'd be grateful if you have an eye on that issue and may help answering > upcoming questions regarding Okular. I've subscribed there. > > Can you try whether setting the "Force rasterization" option in the "PDF > > options" tab of the print dialog works for you as a workaround? > > Indeed, "Force rasterization" workarounds the issue. > > I guess enabling rasterization by default would cause other problems? > (I actually didn't open this issue for myself, but because other users have > the same problem in the company I'm working for - so I'd be grateful for a > general solution) Rasterization basically means that images are generated, so the files can become rather large, which can e.g. result in more memory being required and/or slower printing. Assuming this is actually a bug somewhere in the CUPS filter chain, I'm closing this bug report as UPSTREAM for now. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422600] Okular is unable to print to fit page
https://bugs.kde.org/show_bug.cgi?id=422600 --- Comment #4 from Michael Weghorn --- And does it work if you explicitly enable rasterization? This might help to avoid issues with the CUPS filter chain, s.a. bug 422690. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422690] Margins often cut when printing (2020 - Okular-1.10.0)
https://bugs.kde.org/show_bug.cgi?id=422690 --- Comment #5 from Michael Weghorn --- Since this works OK with CUPS-PDF and the same issue happens when printing using command line, I think this is not an Okular issue, but rather somewhere in the CUPS filter chain. Closing as RESOLVED UPSTREAM accordingly. (In reply to kolAflash from comment #4) > Could you ask the Evince/Gnome people for advice? > Maybe it's a special trick they are intentionally applying. > Because with Evince it's really everything correct. Evince generates PDF print data, whereas Okular (by default) generates PostScript print data, so the CUPS filter chain is a different one in that case. Can you try whether setting the "Force rasterization" option in the "PDF options" tab of the print dialog works for you as a workaround? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422600] Okular is unable to print to fit page
https://bugs.kde.org/show_bug.cgi?id=422600 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de --- Comment #3 from Michael Weghorn --- Works fine for me in a quick test with Okular 1.10.2 on Debian testing using the CUPS-PDF printer using A4 as page size. Does it work for you when "printing" using CUPS-PDF instead of the actual printer as well? If so, you please attach: * your printer's PPD file, located at /etc/cups/.ppd * CUPS log (or relevant part of that for the print job): /var/log/cups/error_log, with 'LogLevel debug' set in /etc/cups/cupsd.conf (might have to set 'ErrorLog /var/log/cups/error_log' in '/etc/cups/cups-files.conf' or otherwise search in journal, depending on how your distro configures this) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 422690] Margins often cut when printing (2020 - Okular-1.10.0)
https://bugs.kde.org/show_bug.cgi?id=422690 Michael Weghorn changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||m.wegh...@posteo.de Status|REPORTED|NEEDSINFO --- Comment #3 from Michael Weghorn --- (In reply to kolAflash from comment #1) > Created attachment 129168 [details] > different logs and printouts (mind extra scanning margins) At a quick glance, the Postscript file generated by Okular looks OK to me (file 'debian_11-beta-20200609/var/spool/cups/d00018-001_-_print-area' in the attached tar file); if you open that in Okular, it looks the same as the PDF file 'numeric_test.pdf'. The processing to fit that to the page etc. is done by CUPS (and the corresponding so-called CUPS filters), according to the options Okular passes, which are those for the first case (from the error_log file): > D [09/Jun/2020:21:25:03 +0200] [Job 18] argv[5]="Collate ColorModel=KGray > finishings=3 fit-to-page job-billing media=A4 number-up=1 > number-up-layout=lrtb outputorder=normal page-bottom=41 page-left=10 > page-right=10 page-top=10 portrait sides=one-sided job-uuid=urn:uuid:c > 7d3001b-0e41-33d2-5eec-70168aa8d6ee job-originating-host-name=localhost > date-time-at-creation= date-time-at-processing= time-at-creation=1591730703 > time-at-processing=1591730703 document-name-supplied=okular_ufzIXL.ps > PageSize=A4" This looks OK to me at a quick glance. Therefore, this might be an issue outside of Okular. Some questions: 1) What happens if you print that file using the same options using command line, i.e.: lp -d HP_DeskJet_1000_at_fbox_hpcups -o "Collate ColorModel=KGray finishings=3 fit-to-page job-billing media=A4 number-up=1 number-up-layout=lrtb outputorder=normal page-bottom=41 page-left=10 page-right=10 page-top=10 portrait sides=one-sided job-uuid=urn:uuid:c 7d3001b-0e41-33d2-5eec-70168aa8d6ee job-originating-host-name=localhost date-time-at-creation= date-time-at-processing= time-at-creation=1591730703 time-at-processing=1591730703 document-name-supplied=okular_ufzIXL.ps PageSize=A4" debian_11-beta-20200609/var/spool/cups/d00018-001_-_print-area 2) Does it make any difference if you just use this command? lp -d HP_DeskJet_1000_at_fbox_hpcups -o fit-to-page debian_11-beta-20200609/var/spool/cups/d00018-001_-_print-area 3) What happens if you print the PDF file numeric_test.pdf_able-job_1474.pdf from Okular to the CUPS-PDF printer instead of your physical one? (seems to work fine for me on Debian testing) 4) Do you have any other printer you can test with, and if so, how does it behave? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 351849] Margins often cut when printing
https://bugs.kde.org/show_bug.cgi?id=351849 Michael Weghorn changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |WORKSFORME --- Comment #43 from Michael Weghorn --- (In reply to kolAflash from comment #40) > Created attachment 129046 [details] > scanned Evince-20.04 and Okular-3.36.1 printings > > I can reproduce the problem with the original attachment: > https://bugs.kde.org/attachment.cgi?id=94244 > [...] Please create a new bug report and leave a link here. (And also attach CUPS's error log with LogLevel set to "debug" in /etc/cups/cupsd.conf, and your printer's PPD, located at /etc/cups/ppd/.ppd) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 422426] Implement Wayland Primary Selection Protocol bridge with XWayland
https://bugs.kde.org/show_bug.cgi?id=422426 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 422340] Portal FileChooser incorrectly handles mnemonics
https://bugs.kde.org/show_bug.cgi?id=422340 --- Comment #2 from Michael Weghorn --- I have a potential fix at [1]. I did not submit a merge request right away, since that commit is on a branch [2] that has more changes for the FileChooser portal, and I think it makes sense to handle the underlying commits first to avoid merge conflicts in the merge requests. For the first two commits, those pending merge requests are [3] and [4]. Please let me know if you want me to submit a merge request for this bug right away instead, and I'll rearrange those commits then. [1] https://invent.kde.org/michaelweghorn/xdg-desktop-portal-kde/-/commit/211b31cad57f332948617cee2d9613e80693169e [2] https://invent.kde.org/michaelweghorn/xdg-desktop-portal-kde/-/tree/michaelweghorn/filechooser_properly_handle_mnemonics_in_accept_label [3] https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/2 [4] https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/3 -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 422340] Portal FileChooser incorrectly handles mnemonics
https://bugs.kde.org/show_bug.cgi?id=422340 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de --- Comment #1 from Michael Weghorn --- Created attachment 128979 --> https://bugs.kde.org/attachment.cgi?id=128979=edit Sample Gtk program to demonstrate the issue. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 422340] New: Portal FileChooser incorrectly handles mnemonics
https://bugs.kde.org/show_bug.cgi?id=422340 Bug ID: 422340 Summary: Portal FileChooser incorrectly handles mnemonics Product: xdg-desktop-portal-kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: jgrul...@redhat.com Reporter: m.wegh...@posteo.de Target Milestone: --- Created attachment 128978 --> https://bugs.kde.org/attachment.cgi?id=128978=edit Screenshot of the portal-native KF5 file save dialog used with simple-scan SUMMARY The FileChooser portal API for 'accept_label' parameter says: > accept_label s > > The label for the accept button. Mnemonic underlines are allowed. However, it seems like xdg-desktop-portal-kde does not properly handle this, but shows literal underscores instead of applying the mnemonics. This can be seen e.g. when using simple-scan (a Gtk application). For the "Save" button, the text "_Save" is shown instead (s. attached screenshot). I'll also attach a small sample Gtk application to reproduce. STEPS TO REPRODUCE 1. compile the attached sample Gtk application that sets the accept label to "S_ave & Done & Finished": gcc -g -O0 -o main_set_save_label $(shell pkg-config --cflags gtk+-3.0) main_set_save_label.cpp $(shell pkg-config --libs gtk+-3.0) 2. run it, using native KF5 file chooser via portal: GTK_USE_PORTAL=1 ./main_set_save_label 3. check the text shown for the confirmation button 4. Press Alt to see what character is being used for the mnemonic for the confirmation button 5. Press Alt+A to confirm (since the mnemonic was supposed to be set for the "a" in the label). OBSERVED RESULT at step 3: The text is "S_ave Done Finished" (with an extra underscore after the 's' and the literal ampersands having gone missing.) at step 4: The "S" is being underlined to indicate that it is the mnemonic. at step 5: An "a" is inserted in the file name box. EXPECTED RESULT at step 3: The text should be is "Save & Done & Finished" (without any extra underscore and containing 2 literal '&'s) at step 4: The "a" should be underlined to indicate that it is the mnemonic. at step 5: The dialog should close. SOFTWARE/OS VERSIONS+ Operating System: Debian GNU/Linux KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.12.5 Kernel Version: 5.6.0-2-amd64 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-5300U CPU @ 2.30GHz Memory: 15.4 GiB of RAM ADDITIONAL INFORMATION xdg-desktop-portal-kde 5.17.5-2 is used. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406053] Top of the page is cut of when printing
https://bugs.kde.org/show_bug.cgi?id=406053
--- Comment #15 from Michael Weghorn ---
(In reply to Matthias from comment #12)
> (In reply to Michael Weghorn from comment #11)
>
> > 1) Did you select any additional information in the print dialog, e.g. set
> > the "Force rasterization" checkbox?
> No, I haven't done anything in particular. Force rasterization is off.
What happens if you switch it on?
> > 2) What margins are set when you check that in the "Properties" dialog in
> > the print dialog? Does changing all margins to 0 make a difference?
> 6.35mm on the left and right, 12.7mm on the top and the bottom. It can't
> change them to 0, the GUI won't allow me to change them to anything less
> than these values.
>
> > 3) What "Scale mode" is selected in the "PDF Options" tab in the print
> > dialog?
> Fit to printable area
That's interesting. At a quick glance, attachment 128311 looks like the missing
content might pretty much match the page margins, i.e. the non-printable area
of the printer ("6.35mm on the left and right, 12.7mm on the top and the
bottom".
However, if "fit to printable area" is selected, the content should
automatically scaled down by CUPS, since it is passed the "fit-to-page" option,
which can also be seen in your error_log:
Mai 09 14:52:14 localhost.localdomain cupsd[126424]: argv[5]="Collate
finishings=3 fit-to-page job-billing media=A4 number-up=1 number-up-layout=lrtb
outputorder=normal page-bottom=36 page-left=18 page-right=18 page-top=36
portrait sides=one-sided job-uuid=urn:uuid:f319f4b2-6461-357b-7ff1-f7b3153c271b
job-originating-host-name=localhost date-time-at-creation=
date-time-at-processing= time-at-creation=1589028734
time-at-processing=1589028734 document-name-supplied=okular_PwkqEO.ps
PageSize=A4"
What happens if you print the original PDF file and the generated PostScript
file using 'lp' from command line, i.e. passing it directly to CUPS rather than
using Okular?
i.e.
lp -d HL-2030-series -o fit-to-page -o PageSize=A4
and
lp -d HL-2030-series -o fit-to-page -o PageSize=A4 d00129-001.ps
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 415986] Printing to HP1120C with gutenprint driver from Okular not working.
https://bugs.kde.org/show_bug.cgi?id=415986 Michael Weghorn changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #9 from Michael Weghorn --- Hi Bruce, (In reply to bruce.samha...@samhaber.ca from comment #6) > Yes this is the same problem as BUG 415985 but with the GUTENPrint driver > (.PPD file) if we should examine the issue with that driver/PPD as well, we'd need the same information that was needed in bug 415985, in particular the PPD and the CUPS error_log. It might well be that this is also an issue with the CUPS filter chain. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985
--- Comment #43 from Michael Weghorn ---
Hi Bruce,
(In reply to bruce.samha...@samhaber.ca from comment #40)
> The problem with the 11x17" paper and Okular is that Okular is only printing
> to letter size (8.5x11") paper no matter what size paper is selected in the
> Printer properties. The files that I am using have the paper size defined in
> the files which Okular is not using.
In my understanding, Okular *should* be using the paper size set in the print
dialog ("Properties" -> "Page Size"). If it does not do so, that sounds like a
bug. Can you attach your error_log from CUPS for a case where you explicitly
selected 11x17 as page size in the print dialog and then printed from there.
And also, can you attach a sample file of that size, so I can check what
happens in my case?
> Also, when I set the paper size in the
> Printer Properties from Okular, then go to the Print Preview it really only
> shows the difference between portrait and landscape with the image scaled to
> fit the paper, the paper size is not indicated. In the Print > Properties
> there is a preview image of the printout showing the orientation Portrait vs
> landscape but it does not include the paper size or the object image on the
> paper.
> So it is never really clear what is going to be printed from the previews.
>
> Should I be opening a new Bug report for the above problem?
The print "preview" shown in the print dialog after pressing "Properties" next
to the printer's name (the "Page") in my case shows the Width and Height of the
page just below the combobox in which the page size can be selected, s.
screenshot in attachment 128611.
That "preview" (which doesn't show the actual content) is part of the Qt print
dialog which Okular and other KDE applications use, so nothing that could be
changed in Okular itself.
As for the print preview in "File" -> "Print Preview", I don't think it takes
into account any of the settings made in the actual print dialog, since those
are only applied for the current printout, i.e. what is done when pressing
"OK".
--
You are receiving this mail because:
You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985 --- Comment #42 from Michael Weghorn --- Created attachment 128611 --> https://bugs.kde.org/attachment.cgi?id=128611=edit Screenshot page properties in print dialog -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985 --- Comment #41 from Michael Weghorn --- (In reply to bruce.samha...@samhaber.ca from comment #39) > Hi Micheal, > Did you need to also set the PDF Option "Use Rasterization" ? Hi Bruce, I did not set "Use Rasterization" in order to try to reproduce the issue that you were encountering when not setting it. So the same case for which the CUPS filter fails in your case works just fine for me, which suggests that the problem is in some other component that differs in your setup from mine on Debian testing. (I don't have a real HP printer to check and am printing to a dummy printer, but if the problem is in the CUPS filter chain, that would show up for me as well) > Is the Cups filter the same as the Foomatic Filter? Yes, it's the same as for your case; the relevant lines in my /var/log/cups/error_log show the same filters: D [19/May/2020:12:01:59 +0200] [Job 1468] 3 filters for job: D [19/May/2020:12:01:59 +0200] [Job 1468] gstopdf (application/postscript to application/pdf, cost 0) D [19/May/2020:12:01:59 +0200] [Job 1468] pdftopdf (application/pdf to application/vnd.cups-pdf, cost 66) D [19/May/2020:12:01:59 +0200] [Job 1468] foomatic-rip (application/vnd.cups-pdf to printer/tofile-hp-1120c-kdebug415985, cost 0) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406053] Top of the page is cut of when printing
https://bugs.kde.org/show_bug.cgi?id=406053 Michael Weghorn changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #11 from Michael Weghorn --- (In reply to Matthias from comment #8) > I've looked at the IPP traffic that I uploaded earlier using Wireshark, and > I found that Okular transmits the data to be printed in PDF format. > > So I extracted that PDF from the pcapng capure file, saved it to disk, > opened it with Okular and found… a blank page with nothing on it. So that > seems to be why nothing is printed. I'm attaching said PDF here in the hope > that it helps to figure out what's going on. That's interesting, since Okular usually generates PostScript for printing by default. Okular does not generate IPP data itself, but uses the 'lpr' or 'lp' command to pass the file to CUPS (or in the case of "Force rasterization" checkbox sent, the Qt library handles passing the file to CUPS). (In reply to Matthias from comment #10) > Created attachment 128311 [details] > Second example after it's been mangled by okular > > This is what's left of the PDF when Okular sends it to CUPS via IPP Some more questions: 1) Did you select any additional information in the print dialog, e.g. set the "Force rasterization" checkbox? 2) What margins are set when you check that in the "Properties" dialog in the print dialog? Does changing all margins to 0 make a difference? 3) What "Scale mode" is selected in the "PDF Options" tab in the print dialog? 4) The file passed to the CUPS Printing system for a print job is saved in /var/spool/cups/d-001. Can you attach that file as well? That should be a PostScript or PDF file. You might have to set 'PreserveJobFiles Yes' in /etc/cups/cupsd.conf in case the file is not present in your case. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985 --- Comment #38 from Michael Weghorn --- I just tried. "Printing" the file to a dummy printer set up with the given PPD file works fine for me on Debian testing, with Okular 1.10.0, CUPS 2.3.3 and cups-filters 1.27.4. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985 Michael Weghorn changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO --- Comment #36 from Michael Weghorn --- (In reply to bruce.samha...@samhaber.ca from comment #35) > I never tried that. > Yes it does print with "Force rasterisation" option set in the print > dialog's "PDF options" section. Thanks for testing. > Is there a way to make this option set by default? As far as I know, there isn't. If you'd still like me to test the bevaviour on Debian testing, please just attach a sample PDF file for which the issue happens for you. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985 --- Comment #34 from Michael Weghorn --- By the way, does printing work if you set the "Force rasterisation" option in the print dialog's "PDF options" section? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985 Michael Weghorn changed: What|Removed |Added Resolution|FIXED |WAITINGFORINFO --- Comment #33 from Michael Weghorn --- (In reply to bruce.samha...@samhaber.ca from comment #14) > I will repeat the whole process just to be sure. > It looked to me like there was lots of old log information in the Error_log > file. Should I clear the Error_log file and how to do that, is it just > delete it? > I notice that there are many lines like > D [28/Apr/2020:19:02:28 -0400] [Job 389] Loading from cache... > every time I print something, but these are all for old jobs that are long > gone. Should I get rid of those, if so how? Thanks for the additional information. Those old entries are no problem. (In reply to bruce.samha...@samhaber.ca from comment #28) > Created attachment 128008 [details] > New /var/log/cups/error_log file This new log file actually contains the relevant information. It looks like a PostScript file is passed to CUPS (printing system) by Okular as expected, but there is a problem in the processing inside of the printing system; a CUPS filter (gstopdf) fails. >From the log file: > D [29/Apr/2020:14:18:38 -0400] [Job 602] pdftopdf: Last filter determined by > the PPD: foomatic-rip; FINAL_CONTENT_TYPE: application/vnd.cups-pdf => > pdftopdf will log pages in page_log. > D [29/Apr/2020:14:18:38 -0400] [Job 602] STATE: -connecting-to-device > D [29/Apr/2020:14:18:38 -0400] cupsdMarkDirty(---J-) > D [29/Apr/2020:14:18:38 -0400] cupsdSetBusyState: newbusy="Printing jobs and > dirty files", busy="Dirty files" > D [29/Apr/2020:14:18:38 -0400] cupsdMarkDirty(S) > D [29/Apr/2020:14:18:38 -0400] cupsdSetBusyState: newbusy="Printing jobs and > dirty files", busy="Printing jobs and dirty files" > D [29/Apr/2020:14:18:38 -0400] [Job 602] Unrecoverable error: rangecheck in > --.trysetparams-- > D [29/Apr/2020:14:18:38 -0400] [Job 602] Operand stack: > D [29/Apr/2020:14:18:38 -0400] [Job 602] true true true --nostringval-- > --nostringval-- --nostringval-- --nostringval-- --nostringval-- > --nostringval-- --nostringval-- --nostringval-- true --nostringval-- > %MediaSource 0 %MediaDestination 0 .LockSafetyParams true > --nostringval-- --nostringval-- --nostringval-- 7 --nostringval-- false > --nostringval-- > D [29/Apr/2020:14:18:38 -0400] [Job 602] PID 5317 > (/usr/lib/cups/filter/gstopdf) stopped with status 1. > > [...] > D [29/Apr/2020:14:18:39 -0400] [Job 602] GPL Ghostscript 9.27: ? eprn: This document requests a page size of 0 x 0 bp. D [29/Apr/2020:14:18:39 -0400] [Job 602] GPL Ghostscript 9.27: This size is not supported as a discrete size and it exceeds the D [29/Apr/2020:14:18:39 -0400] [Job 602] custom page size limits for the HP DeskJet 1120C. D [29/Apr/2020:14:18:39 -0400] [Job 602] Unable to open the initial device, quitting. D [29/Apr/2020:14:18:39 -0400] [Job 602] renderer exited with status 1 D [29/Apr/2020:14:18:39 -0400] [Job 602] Possible error on renderer command line or PostScript error. Check options.Kid3 exit status: 3 D [29/Apr/2020:14:18:39 -0400] [Job 602] PID 5319 (/usr/lib/cups/filter/foomatic-rip) stopped with status 9. D [29/Apr/2020:14:18:39 -0400] [Job 602] PID 5320 (/usr/lib/cups/backend/parallel) exited with no errors. It looks like there probably isn't much that can be done from Okular side in this case. Does this happen for every file you're trying to print? Can you attach a sample file, so I can test whether the filter fails the same way for me on Debian testing? What version of the package cups-filters do you have? (as far as I I know, that is the package that provides the gstopdf filter.) (In reply to Christoph Feck from comment #32) > Okular uses QPrintDialog. If it lists more/different printers than you have > available, then it would be a bug there. This was already seen in bug > 417186, but I don't know if the reporter opened a ticket at the Qt bug > tracker. Yes, I suppose this additional printer also shows up in other KDE applications, e.g. Kate? In case you plan to open a separate bug report for this, please leave a link here. The 'lpstat -v' output might be helpful to find out more about this. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 406053] Top of the page is cut of when printing
https://bugs.kde.org/show_bug.cgi?id=406053 Michael Weghorn changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||m.wegh...@posteo.de Status|REPORTED|NEEDSINFO --- Comment #1 from Michael Weghorn --- Some questions to narrow this further down: 1) Can you attach the PPD file of the printer, which should be located at /etc/cups/ppd/.ppd ? 2) Can you attach a CUPS debug log when doing such a printout? (set 'LogLevel debug' in /etc/cups/cupsd.conf, then restart CUPS, print, and attach /var/log/cups/error_log (or the relevant part of it). (Depending on the setting for 'ErrorLog' in /etc/cups/cups-files.conf, the log output may alternatively go to the journal, so either retrieve it from there or set 'ErrorLog /var/log/cups/error_log' -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985 Michael Weghorn changed: What|Removed |Added Status|REOPENED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #13 from Michael Weghorn --- (In reply to bruce.samha...@samhaber.ca from comment #9) > Please let me know if these are the correct attachments then I will change > to the Gutenprint.ppd and create the error_log file for the other Bug > report. Thanks for the attachments. The CUPS error_log however does not seem to contain the debug log information of an actual printout (there should e.g. be various lines containing "argv"). Did you actually try to print from Okular after enabling LogLevel debug? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985 --- Comment #5 from Michael Weghorn --- Note: There's also bug 415986 describing mostly the same issue for the same printer with another PPD/driver in use. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415986] Printing to HP1120C with gutenprint driver from Okular not working.
https://bugs.kde.org/show_bug.cgi?id=415986 Michael Weghorn changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||m.wegh...@posteo.de --- Comment #5 from Michael Weghorn --- Do I understand correctly that this is basically the same bug report as 415985 (also reported by you), just for another driver/PPD? If so, please answer the same questions as asked in bug 415985 comment 4? (In reply to bruce.samha...@samhaber.ca from comment #4) > Any advise on how to get a driver to use the full features of the printer > including the special feature - banner mode? That depends on the PPD/driver you're using, so I'd suggest to check whether you can find another one for that model. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 415985] Okular is not printing to HP1120C printer with driver HP DeskJet 1120C Foomatic/pcl3
https://bugs.kde.org/show_bug.cgi?id=415985 Michael Weghorn changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||m.wegh...@posteo.de --- Comment #4 from Michael Weghorn --- Some questions to narrow down the issue: 1) Does printing from other Qt/KDE applications work, e.g. Kate? 2) Can you attach the PPD of the printer, located at /etc/cups/ppd/.ppd? 3) Can you please attach the CUPS debug log which can be retrieved as described in bug 418551 comment 1 ? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 418551] Duplex printing setting ignored
https://bugs.kde.org/show_bug.cgi?id=418551 Michael Weghorn changed: What|Removed |Added CC||m.wegh...@posteo.de Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Michael Weghorn --- For further analysis, can you please attach: 1) the PPD of the printer, located at /etc/cups/ppd/.ppd 2) a CUPS debug log of one such printout (set 'LogLevel debug' in /etc/cups/cupsd.conf, then restart CUPS, print, and attach /var/log/cups/error_log (or the relevant part of it). (Depending on the setting for 'ErrorLog' in /etc/cups/cups-files.conf, the log output may alternatively go to the journal, so either retrieve it from there or set 'ErrorLog /var/log/cups/error_log'). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 407998] Okular scales down pages when printing
https://bugs.kde.org/show_bug.cgi?id=407998 --- Comment #16 from Michael Weghorn --- (In reply to Éric Brunet from comment #15) > (In reply to Michael Weghorn from comment #11) > > This is https://phabricator.kde.org/D10974 and I quickly verified that > > current development version of Okular actually offers either "Fit to > > printable area" or "Fit to full page" when opening a TIFF file. > > This is very good indeed, but it seems to me a third option is needed: > Keep the actual image size and do no scaling at all > > At the moment, if I load a pdf of size 15cm x 8cm, I do not know how to > print it to have a 15cm x 8cm picture in the middle of an empty A4 sheet of > paper. > > Or did I miss an option somewhere ? At least in Okular 1.9.3, you can select this for the scale mode in the "PDF Options" tab: "None; print original size". It should do exactly what you want. -- You are receiving this mail because: You are watching all bug changes.
