[korganizer] [Bug 412722] KOrganizer does not show events from EWS resource
https://bugs.kde.org/show_bug.cgi?id=412722 --- Comment #6 from Martin Höher --- Sorry to spam here, but: Any updates on the topics? I just checked again with the latest KOrganizer installed from Fedora repositories (it shows version 5.19.2 (21.12.2) in the about dialog. I still see the same: Events created by myself seem to work but not ones I've been invited to. Interestingly, all of the events properly show up in akonadiconsole, too - including start/end time, message body, ... Could that help debugging the issue further? -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 412722] KOrganizer does not show events from EWS resource
https://bugs.kde.org/show_bug.cgi?id=412722 --- Comment #7 from Martin Höher --- And another observation: It seems that this issue only occurs with an Office 365 account. On work, we have two accounts, an O365 one (with that one I have this problem) and an in-house Exchange server (and here - it seems - all events are properly showing up). So, could this be due to the server version (O365 is running always on latest greatest while the in house server is on Exchange 2016 version). -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 412722] KOrganizer does not show events from EWS resource
https://bugs.kde.org/show_bug.cgi?id=412722 --- Comment #8 from Martin Höher --- I'm really sorry and promise I will stop spamming. But just in case this helps: I just found kalendar (https://github.com/KDE/kalendar) and tried it - but it has the same issues. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439815] Window randomly become transparent, when close ghost image remains
https://bugs.kde.org/show_bug.cgi?id=439815 Martin Höher changed: What|Removed |Added CC||mar...@rpdev.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439815] Window randomly become transparent, when close ghost image remains
https://bugs.kde.org/show_bug.cgi?id=439815 --- Comment #15 from Martin Höher --- I can support the observation that MarkH made: I am on Fedora 34, KDE installed from the Fedora repositories (Plasma v5.22.5, KDE frameworks v5.85.0, Qt 5.15.2). I regularly get the same transparent window effect. Restarting kwin fixes this, but afterwards everything is unusably slow. -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 435364] New: Adding QtRemoteObjects to the KDE Flatpak Runtime
https://bugs.kde.org/show_bug.cgi?id=435364 Bug ID: 435364 Summary: Adding QtRemoteObjects to the KDE Flatpak Runtime Product: Qt/KDE Flatpak Runtime Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: mar...@rpdev.net CC: aa...@kde.org Target Milestone: --- SUMMARY It would be great if the QtRemoteObjects module could be added to the KDE flatpak runtime. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I am developing an app based on Qt5 (borrowing some functionality from KDE Tier 1 frameworks - thanks a lot for these ;-)) which I, among other target channels, also release as Flatpak (which is build using the KDE flatpak runtime as a base - also a big thanks for this one). In this app I use the QtRemoteObjects module: It is a cross platform approach for IPC. In that regard, somehow similar to Dbus. Currenlty, QtRemoteObjects does not seem to be part of the KDE flatpak runtime. I managed to install it manually during the build of my app, but that feels kind of hacky. I guess, this would be easier with future Qt versions (aka Qt 6) as then cmake is used for building Qt which makes building and installing Qt "core" libraries into non-Qt/system locations in such a scenario easier. I still wonder, if QtRemoteObjects could be added to the KDE flatpak runtime? I have no idea how heavily this part of Qt is used and if it is worth adding it, but personally, I found it really convenient, as it allows easy IPC in a really cross-platform way (i.e. also on Android). Thanks for considering! -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 435364] Adding QtRemoteObjects to the KDE Flatpak Runtime
https://bugs.kde.org/show_bug.cgi?id=435364 --- Comment #3 from Martin Höher --- Great, thanks a lot! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431234] Dolphin does not remember its window size
https://bugs.kde.org/show_bug.cgi?id=431234 Martin Höher changed: What|Removed |Added CC||mar...@rpdev.net --- Comment #10 from Martin Höher --- I can confirm this bug. I had it once and IIRC "solved" it by deleting the dolphinrc file. However, now the behaviour is back. What I find interesting... I tried the following: - Quit dolphin - Removed that file - Started dolphin again Dolphin still came up with the same, wrong window size. But otherwise, it still remembered all of the other settings (e.g. the last folder it has been in). It somehow seems like the config is cached somewhere and not updated, no matter if that file is removed or not. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431234] Dolphin does not remember its window size
https://bugs.kde.org/show_bug.cgi?id=431234 --- Comment #13 from Martin Höher --- (In reply to Claudius Ellsel from comment #12) > (In reply to Martin Höher from comment #10) > > Dolphin still came up with the same, wrong window size. But otherwise, it > > still remembered all of the other settings (e.g. the last folder it has been > > in). It somehow seems like the config is cached somewhere and not updated, > > no matter if that file is removed or not. > > Good to know I am not alone with this. Can you add some details about your > setup (Distribution, X11 or Wayland, other special things like multiple > monitors)? Also, what was the wrong window size? 640x480? Sure. I am on Fedora 33, X11. I am using a dual-monitor setup, with a laptop and - attached to it an external 4K monitor. Dolphin says it is at version 20.08.3. For me, the window size seems to be fixed to 1920x740 (so, rather large). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 431234] Dolphin does not remember its window size
https://bugs.kde.org/show_bug.cgi?id=431234 --- Comment #16 from Martin Höher --- (In reply to Claudius Ellsel from comment #14) > Multi monitor it is. After deactivating one of mine, it works for me again. > > As I suspected in the original bug report, this is strongly related, maybe > even a duplicate of https://bugs.kde.org/show_bug.cgi?id=427875. Having > played around a bit, I am rather sure it is a duplicate. I will first mark > the Konsole and Dolphin spin off as duplicate of my original report and then > mark the as duplicate of https://bugs.kde.org/show_bug.cgi?id=427875. > > (Martin, I am assuming that you have the same problem, but please check > whether this is correct, else we can track the bug you are experiencing > somewhere else) Yes, I can confirm: If I unplug the external monitor, everything is fine and Dolphin remembers the window size properly between restarts. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kconfig] [Bug 427875] Windows do not remember size, position, or the screen they were last opened on when the left-most display is not the primary one
https://bugs.kde.org/show_bug.cgi?id=427875 Martin Höher changed: What|Removed |Added CC||mar...@rpdev.net -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 412722] New: KOrganizer does not show events from EWS resource
https://bugs.kde.org/show_bug.cgi?id=412722 Bug ID: 412722 Summary: KOrganizer does not show events from EWS resource Product: korganizer Version: 5.11.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: mar...@rpdev.net Target Milestone: --- SUMMARY Events from an EWS resource are not shown in KOrganizer. STEPS TO REPRODUCE 1. Set up an EWS resource 2. Make sure, e-mails show up in KMail. OBSERVED RESULT In KOrganizer, no events are shown. EXPECTED RESULT KOrganizer should show events synced via EWS. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 30, Kontact 5.11.2 (available in About System) KDE Plasma Version: 5.15.5 KDE Frameworks Version: 5.59.0 Qt Version: 5.12.4 ADDITIONAL INFORMATION The EWS sync for mails works properly, i.e. I can see and write mails via KMail. The calendar folders are also showing up, however, there are no events shown in neither view of KOrganizer. The most interesting part however is, that the events are shown in the calendar plasmoid via the PIM events plugin. So it seems, internally Akonadi syncs these items. They are "just not drawn" by KOrganizer... -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 412722] KOrganizer does not show events from EWS resource
https://bugs.kde.org/show_bug.cgi?id=412722 --- Comment #1 from Martin Höher --- Btw: I just realized than when scrolling back a bit in the calendar into past months, I see some (but not all) events I had. So KOrganizer internally seems to see at least a subset of the items available on the server and probably fetched by Akonadi. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 412722] KOrganizer does not show events from EWS resource
https://bugs.kde.org/show_bug.cgi?id=412722 --- Comment #2 from Martin Höher --- Another observation: It seems that KOrganizer renders events which I created myself (via the Office 365 web interface). But ones created by others (where I am just invited) are not shown. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-syntax-highlighting] [Bug 405661] New: Cross-mingw64 compilation: Cannot compile app using syntax highlighting framework
https://bugs.kde.org/show_bug.cgi?id=405661 Bug ID: 405661 Summary: Cross-mingw64 compilation: Cannot compile app using syntax highlighting framework Product: frameworks-syntax-highlighting Version: 5.56.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: framework Assignee: kwrite-bugs-n...@kde.org Reporter: mar...@rpdev.net Target Milestone: --- SUMMARY In a Fedora mingw64 cross compile environment for Windows, in an app using the syntax highlighting framework, compilation fails with the following error: In file included from /usr/i686-w64-mingw32/sys-root/mingw/include/c++/ext/string_conversions.h:41, from /usr/i686-w64-mingw32/sys-root/mingw/include/c++/bits/basic_string.h:6400, from /usr/i686-w64-mingw32/sys-root/mingw/include/c++/string:52, from /usr/i686-w64-mingw32/sys-root/mingw/include/c++/stdexcept:39, from /usr/i686-w64-mingw32/sys-root/mingw/include/c++/array:39, from /usr/i686-w64-mingw32/sys-root/mingw/include/c++/tuple:39, from /usr/i686-w64-mingw32/sys-root/mingw/include/c++/functional:54, from ../lib/datamodel/library.h:4, from ../lib/application.h:4, from ../lib/application.cpp:1: /usr/i686-w64-mingw32/sys-root/mingw/include/c++/cstdlib:75:15: fatal error: stdlib.h: No such file or directory #include_next ^~ STEPS TO REPRODUCE 1. Set up mingw64 cross compile environment in Fedora by installing from repository. 2. Install ECM and syntax-highlighting framework from source. 3. Try to compile an app which uses cmake and which compiles and links against the syntax highlighting library. OBSERVED RESULT Compilation fails (e.g. when #include is used). EXPECTED RESULT Compilation works fine. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.56.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION I am developing an app which I also want to compile for Windows. For this purpose, I am using the mingw64 packages provided by Fedora. Qt 5 is provided as part of these packages as well. I am using Docker for this. To reproduce, you can create a Docker image using the following Dockerfile: = FROM fedora RUN \ \ dnf install -y --nogpgcheck \ cmake \ make \ ninja-build \ python3 \ python \ git \ wget \ \ qt5-qtxmlpatterns-devel \ qt5-linguist \ appstream \ \ mingw32-qt5-qmake \ mingw32-qt5-qmldevtools \ mingw32-qt5-qmldevtools-devel \ mingw32-qt5-qt3d \ mingw32-qt5-qt3d-tools \ mingw32-qt5-qtactiveqt \ mingw32-qt5-qtbase \ mingw32-qt5-qtbase-devel \ mingw32-qt5-qtcharts \ mingw32-qt5-qtdeclarative \ mingw32-qt5-qtgraphicaleffects \ mingw32-qt5-qtimageformats \ mingw32-qt5-qtlocation \ mingw32-qt5-qtmultimedia \ mingw32-qt5-qtquickcontrols \ mingw32-qt5-qtsensors \ mingw32-qt5-qtserialport \ mingw32-qt5-qtsvg \ mingw32-qt5-qttools \ mingw32-qt5-qttools-tools \ mingw32-qt5-qttranslations \ mingw32-qt5-qtwebkit \ mingw32-qt5-qtwebsockets \ mingw32-qt5-qtwinextras \ mingw32-qt5-qtxmlpatterns \ mingw32-nsis \ mingw32-nsiswrapper \ \ && \ cd / && \ git clone https://github.com/qt/qtquickcontrols2.git && \ cd qtquickcontrols2 && \ git checkout v$(mingw32-qmake-qt5 -query QT_VERSION) && \ mingw32-qmake-qt5 && \ make -j4 && \ make install && \ cd .. && \ rm -rf qtquickcontrols2 = In my app, I also want to use the syntax highlighting framework. As this library is not part of the mingw packages included in Fedora, I compile and install both ECM and the syntax highlighting framework as part of my build script: # Install ECM pushd 3rdparty/KDE/extra-cmake-modules mkdir -p build cd build mingw32-cmake -GNinja .. cmake --build . cmake --build . --target install popd # Install KDE syntax highlighting pushd 3rdparty/KDE/syntax-highlighting mkdir -p build cd build mingw32-cmake -GNinja -DKF5_HOST_TOOLING=/usr .. cmake --build . cmake --build . --target install popd After this is done, I try to compile my own app, which, among other things, does the following to include the syntax highlighting library: # Find KDE Syntax Highlighting engine find_package(KF5SyntaxHighlighting) if(KF5SyntaxHighlighting_FOUND) set(LIB_LIBRARIES ${LIB_LIBRA
[kwin] [Bug 360978] Tooltips (task manager, system tray) are rendered incorrectly
https://bugs.kde.org/show_bug.cgi?id=360978 --- Comment #12 from Martin Höher --- Hey guys, I just wanted to let you know that after running an update today to Plasma 5.7.1 (from Fedora packages) the described issue seems to be gone :-) So whatever fixed it: Thank you a lot (also in general, so far I love the 5.7 release)! Ciao Martin -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 360482] New: Importing an OpenVPN configuration with embedded certificates yields a defect connection due to SELinux
https://bugs.kde.org/show_bug.cgi?id=360482 Bug ID: 360482 Summary: Importing an OpenVPN configuration with embedded certificates yields a defect connection due to SELinux Product: plasma-nm Version: 5.5.5 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: minor Priority: NOR Component: editor Assignee: lu...@kde.org Reporter: mar...@rpdev.net CC: jgrul...@redhat.com I tried to import an OpenVPN configuration file with embedded certificates (via File -> Import VPN...). The configuration is correctly imported. When being asked whether to copy the embedded certificates, I answered yes. In my case, I had to edit the newly created connection to enter my personal OpenVPN user name and password. When trying to connect to the VPN, the connection fails. This is due to the imported certificates in $HOME/.local/share/networkmanagement/certificates/$VPN_CON_NAME have an incorrect SELinux context: $ ls -lZ -rw-rw-r--. 1 martin martin unconfined_u:object_r:data_home_t:s0 2317 Mär 13 17:02 ca.crt -rw-rw-r--. 1 martin martin unconfined_u:object_r:data_home_t:s0 602 Mär 13 17:02 tls_auth.key When I run `restorecon *` in that directory, the type context of the files get changed: $ ls -lZ -rw-rw-r--. 1 martin martin unconfined_u:object_r:home_cert_t:s0 2317 Mär 13 17:02 ca.crt -rw-rw-r--. 1 martin martin unconfined_u:object_r:home_cert_t:s0 602 Mär 13 17:02 tls_auth.key Now, connecting to the VPN works as expected. I think the import process should automatically set the correct SELinux context when opening the configuration. Reproducible: Always Steps to Reproduce: 1. In the connection editor, use File -> Import VPN... 2. When being asked whether to copy the embedded certificates, answer "Yes". 3. If required, edit the newly created connection to e.g. provide your VPN user name and password. 4. Try to connect. Actual Results: The connection fails. Expected Results: The connection should be properly established. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360978] New: Tooltips (task manager, system tray) are rendered incorrectly
https://bugs.kde.org/show_bug.cgi?id=360978 Bug ID: 360978 Summary: Tooltips (task manager, system tray) are rendered incorrectly Product: plasmashell Version: 5.5.95 Platform: Fedora RPMs OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: mar...@rpdev.net CC: bhus...@gmail.com, plasma-b...@kde.org After updating to Plasma 5.5.95, the tooltips are rendered incorrectly. This is most notable with the task manager, but also visible with the system tray (I guess also everything else providing tooltips is affected). When e.g. moving the mouse cursor between different entries in the task manager, the tooltips get rendered incorrectly. The problem seems to occur only when I am not on the virtual desktop 1. As soon as I change to virtual desktop 1, the tooltips are rendered as expected. Reproducible: Always Steps to Reproduce: 1. Switch to a virtual desktop other than desktop 1. 2. Move the mouse cursor e.g. over an entry in task manager and wait for the tool tip to appear. 3. Move the mouse to another task manager entry. Actual Results: The tooltip is rendered incorrectly. It looks like the rectangle is split up into multiple pieces. Expected Results: The tooltip is rendered correctly. I am using the beta RPMs from the KDE SIG Copr repository: https://copr.fedorainfracloud.org/coprs/g/kdesig/plasma-5-unstable/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360978] Tooltips (task manager, system tray) are rendered incorrectly
https://bugs.kde.org/show_bug.cgi?id=360978 --- Comment #1 from Martin Höher --- Created attachment 98077 --> https://bugs.kde.org/attachment.cgi?id=98077&action=edit Screenshot showing an incorrectly rendered tooltip. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 360978] Tooltips (task manager, system tray) are rendered incorrectly
https://bugs.kde.org/show_bug.cgi?id=360978 --- Comment #2 from Martin Höher --- I just realized that the problem does not appear if the "Morphing Popups" effect is turned off in System Settings -> Desktop Effects. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360978] Tooltips (task manager, system tray) are rendered incorrectly
https://bugs.kde.org/show_bug.cgi?id=360978 --- Comment #5 from Martin Höher --- Created attachment 98223 --> https://bugs.kde.org/attachment.cgi?id=98223&action=edit Output of `qdbus org.kde.KWin /KWin supportInformation` -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360978] Tooltips (task manager, system tray) are rendered incorrectly
https://bugs.kde.org/show_bug.cgi?id=360978 --- Comment #6 from Martin Höher --- As recommended, I tried to disable the blur and contrast effects and enabling the morphing popups effect, but the issue remains. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360978] Tooltips (task manager, system tray) are rendered incorrectly
https://bugs.kde.org/show_bug.cgi?id=360978 --- Comment #8 from Martin Höher --- Switching to GLX did not change anything. What I just noticed is that the issue also occurs on VD1, so this was a false trace (dunno why it did not seem to happen on VD1 before, though...). Regarding DRI3, this is what I found in the X log: [14.847] (II) intel(0): direct rendering: DRI2 DRI3 enabled So I guess DRI3 is in fact enabled already. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 360978] Tooltips (task manager, system tray) are rendered incorrectly
https://bugs.kde.org/show_bug.cgi?id=360978 --- Comment #11 from Martin Höher --- No problem, survived worse ;) Regarding OpenGL: I tried to switch to 2.0 which does not change anything. Switching to XRender makes some difference (there are still fragments seen on the screen, but compared to OpenGL - where the fragments are kind of flickering - with XRender the fragments are drawn steadily). -- You are receiving this mail because: You are watching all bug changes.