[plasmashell] [Bug 421392] plasmashell crashes when opening the thermal monitor widget settings
https://bugs.kde.org/show_bug.cgi?id=421392 Alexander Kandaurov changed: What|Removed |Added CC||aakandau...@yandex.ru --- Comment #23 from Alexander Kandaurov --- Did a git bisect on plasma-frameworks, the breaking commit is 48f60533b92231c706da3c9ff0f62cff206ee8d5. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419156] task manager doesn't work during "show desktop"
https://bugs.kde.org/show_bug.cgi?id=419156 Alexander Kandaurov changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |DUPLICATE CC||aakandau...@yandex.ru --- Comment #1 from Alexander Kandaurov --- *** This bug has been marked as a duplicate of bug 392289 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392289] After activating "Show desktop, " clicking on window in task manager does not get focus properly
https://bugs.kde.org/show_bug.cgi?id=392289 Alexander Kandaurov changed: What|Removed |Added CC||mat...@fh-aachen.de --- Comment #5 from Alexander Kandaurov --- *** Bug 419156 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 392289] After activating "Show desktop, " clicking on window in task manager does not get focus properly
https://bugs.kde.org/show_bug.cgi?id=392289 Alexander Kandaurov changed: What|Removed |Added CC||aakandau...@yandex.ru --- Comment #4 from Alexander Kandaurov --- Looks like this bug belongs to kwin and was introduced by a fix to bug 375993. When calling Workspace::activateClient(), Workspace::setShowingDesktop() is called and with the code from that fix added it ends up activating a wrong window. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 373075] Changing Resolution hides programs in task manager
https://bugs.kde.org/show_bug.cgi?id=373075 Alexander Kandaurov changed: What|Removed |Added CC||marti...@mailfence.com --- Comment #25 from Alexander Kandaurov --- *** Bug 400505 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 400505] Tasks disappear after resolution changes
https://bugs.kde.org/show_bug.cgi?id=400505 Alexander Kandaurov changed: What|Removed |Added CC||aakandau...@yandex.ru Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Alexander Kandaurov --- *** This bug has been marked as a duplicate of bug 373075 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 382374] Second Screen Desktop config lost after turning off and on both DP-Displays
https://bugs.kde.org/show_bug.cgi?id=382374 Alexander Kandaurov changed: What|Removed |Added CC||aakandau...@yandex.ru --- Comment #6 from Alexander Kandaurov --- When I disconnect both my monitors off and then reconnect them (first disconnect primary, then secondary, then reconnect in the same order), the ScreenConnectors section in my ~/.config/plasmashellrc file changes from this: [ScreenConnectors] 0=HDMI-1 1=VGA-1 to this: [ScreenConnectors] 0=HDMI-1 1=:0.0 2=VGA-1 So, basically what happens is that some generic screen with a name :0.0 appears and gets assigned an ID, then when the second monitor is reconnected back, its previous ID is already taken and thus becomes 2, and whatever desktop configuration that exists for screen 2 (none) is shown on it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 393881] Desktop widget position lost after reboot
https://bugs.kde.org/show_bug.cgi?id=393881 Alexander Kandaurov changed: What|Removed |Added CC||aakandau...@yandex.ru --- Comment #15 from Alexander Kandaurov --- I also experience a similar behavior and did some research on it. First of all, in my case the bug is triggered when a) the screen configuration at the login screen is different from what is set up in KDE settings, and b) the screen configuration change happens after plasmashell has already started and loaded some widgets. So, a possible workaround is to configure your monitors system-wide to match KDE settings. Here is a possible way to do it: https://forum.manjaro.org/t/dm-multi-monitor-configuration/99978 Now to the details. There are at least two mechanisms leading to this bug. The first of them is the widget position rescaling that is intended to be triggered by a resolution change when Plasma is running, but what actually happens at startup is the following. Suppose we are switching a single screen from a higher to a lower resolution. Initially, the widgets are laid out to their saved positions from the config file which are based on the resolution that should be set when Plasma is up and running. Then, upon a resolution change, the previous AppletsLayout item size gets saved, which at that point matches the whole previous resolution, and then, near the end of Plasma startup, gets compared to the new size, which, aside from corresponding to a different resolution, is further affected by the now loaded panels sizes subtracted, and a rescaling is done. Now, if there are two monitors of different resolution connected and the primary screen gets changed, which was my actual initial case (although in my case the monitor arrangement was also different), then the new and the saved layout sizes get swapped (and further subtracted the panel heights), which is probably caused by ID mismatch in (m_containment->screen() == id) comparison in appletslayout.cpp. The second one happens when a resolution is changed from a lower one. In this case, the window size and the AppletsLayout size don't change immediately after the resolution changes. Actually, their sizes may stay equal to the old resolution for several seconds. And the resizing itself may also be tricky, involving reverting resizes and going through animation sequences. Initially, the applets are correctly laid out to their saved coordinates, but then m_configKeyChangeTimer gets activated and calls m_layoutManager->resetLayoutFromConfig(), which repositions the widgets while watching them not to fall out of the layout boundaries, which have not been updated yet. Then the first mechanism comes in to make things even worse. Rotating a screen basically triggers the same mechanism, the main difference being that initially all the widgets are shown up as a mess in the corner before setConfigKey is called. All the testing was done on X11. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 417570] in KDE Neon 5.18 LibreOffice without gtk has a very wrong layout
https://bugs.kde.org/show_bug.cgi?id=417570 --- Comment #13 from Alexander Kandaurov --- (In reply to Beurt from comment #11) libreoffice-kde5 is available from ppa:libreoffice/libreoffice-6-3. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 417570] in KDE Neon 5.18 LibreOffice without gtk has a very wrong layout
https://bugs.kde.org/show_bug.cgi?id=417570 Alexander Kandaurov changed: What|Removed |Added CC||aakandau...@yandex.ru --- Comment #10 from Alexander Kandaurov --- In my case, the bug with window layouts shifted upwards beyond the window border is exhibited when libreoffice-kde5 is not installed and installing libreoffice-kde5 fixes it. I use KDE neon with Plasma 5.18.0 and LibreOffice 6.3.4.2. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 396087] Okular stops rendering some pages, locks up at 25% CPU usage and won't die
https://bugs.kde.org/show_bug.cgi?id=396087 Alexander Kandaurov changed: What|Removed |Added CC||aakandau...@yandex.ru --- Comment #7 from Alexander Kandaurov --- I investigated this a bit and it looks like what causes the hang is the QTimer::singleShot() call from Generator::generatePixmap() which keeps an endless cycle of firing and resetting the same timer. I also experienced a hang once on closing a document (the window has closed but the process remained eating 25% of CPU) where it got stuck in DocumentPrivate::clearAndWaitForRequests() on loop.exec() call where it also kept firing that generatePixmap() timer. -- You are receiving this mail because: You are watching all bug changes.
