[krita] [Bug 467897] brush hardness and opacity blending bug
https://bugs.kde.org/show_bug.cgi?id=467897 --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/graphics/krita/-/merge_requests/1782 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 461385] The app just does a refresh
https://bugs.kde.org/show_bug.cgi?id=461385 --- Comment #26 from jonzn4SUSE --- After the pam update, all is well. Carry on... -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 461385] The app just does a refresh
https://bugs.kde.org/show_bug.cgi?id=461385 --- Comment #25 from jonzn4SUSE --- Created attachment 157944 --> https://bugs.kde.org/attachment.cgi?id=157944=edit Just more detail -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 461385] The app just does a refresh
https://bugs.kde.org/show_bug.cgi?id=461385 --- Comment #24 from jonzn4SUSE --- Created attachment 157943 --> https://bugs.kde.org/attachment.cgi?id=157943=edit This is what I get when updaing pam On this laptop I'm going to proceed. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 461385] The app just does a refresh
https://bugs.kde.org/show_bug.cgi?id=461385 --- Comment #23 from jonzn4SUSE --- Created attachment 157942 --> https://bugs.kde.org/attachment.cgi?id=157942=edit same issue Same issue on another laptop. Operating System: openSUSE Tumbleweed 20230331 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.8-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i7-4810MQ CPU @ 2.80GHz Memory: 31.0 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 4600 Manufacturer: Hewlett-Packard Product Name: HP ZBook 17 G2 System Version: A3009DD10303 -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 468265] Gwenview can't save KFileDialog Settings properly
https://bugs.kde.org/show_bug.cgi?id=468265 --- Comment #1 from Mintra --- Created attachment 157941 --> https://bugs.kde.org/attachment.cgi?id=157941=edit Save dialog -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 468265] New: Gwenview can't save KFileDialog Settings properly
https://bugs.kde.org/show_bug.cgi?id=468265 Bug ID: 468265 Summary: Gwenview can't save KFileDialog Settings properly Classification: Applications Product: gwenview Version: 22.12.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: hedim74...@fgvod.com Target Milestone: --- Created attachment 157940 --> https://bugs.kde.org/attachment.cgi?id=157940=edit Side panel icon change SUMMARY *** Gwenview can't properly save [KFileDialog Settings] settings. It always reverts back. *** STEPS TO REPRODUCE 1. Open Gwenview, change the places pane icon size to 16x16. 2. Reopen Gwenview, the icon size will reverts back to original 3. Same thing happens with file saving dialog, change the side panel icon size, reopen the app and it will revert back to original 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 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467897] brush hardness and opacity blending bug
https://bugs.kde.org/show_bug.cgi?id=467897 sh_zam changed: What|Removed |Added CC||dimul...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468217] xf86-input-libinput 1.3.0 DPI and mouse acceleration issue on KDE Plasma X11
https://bugs.kde.org/show_bug.cgi?id=468217 fi...@zzls.xyz changed: What|Removed |Added CC||fi...@zzls.xyz --- Comment #2 from fi...@zzls.xyz --- I can confirm this issue, selecting either "Flat" or "Adaptive" doesn't change the mouse acceleration. In this new version of `xf86-input-libinput` they added another `profile` which is the `LIBINPUT_CONFIG_ACCEL_PROFILE_CUSTOM` (at `./src/xf86libinput.c` line `5590` in the source code) adding a third value to the libinput acceleration profile settings and somewhat breaking KDE Plasma Mouse settings. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 466985] memory leak
https://bugs.kde.org/show_bug.cgi?id=466985 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 467737] cant wrte
https://bugs.kde.org/show_bug.cgi?id=467737 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467707] Dolphin crash on watch video on preview panel
https://bugs.kde.org/show_bug.cgi?id=467707 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 422798] While dealing cards strange things appear on the screen
https://bugs.kde.org/show_bug.cgi?id=422798 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 467552] Powerdevil Crashes When Unlocking Screen After Powersaving
https://bugs.kde.org/show_bug.cgi?id=467552 --- Comment #5 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 459392] warning: The macro `AC_PROG_CC_C99' is obsolete
https://bugs.kde.org/show_bug.cgi?id=459392 --- Comment #3 from Dustin Hacker --- (In reply to Dustin Hacker from comment #2) > I was able to correct this and run autogen.sh completely by changing > > 'AC_PROG_CC_C99' > > to > > 'AC_PROG_CC' > > in the configure.ac file on the line mentioned by @Ömer Fadıl USTA in > comment 1. > > This is correct in accordance with > https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.71/ > html_node/C-Compiler.html#AC_005fPROG_005fCC because AC_PROG_CC replaced the > obsolete AC_PROG_CC_C99 autoconf macro. Forgot to mention that I found this solution here https://gitlab.com/openconnect/openconnect/-/issues/413 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468108] ledger freeze on large account
https://bugs.kde.org/show_bug.cgi?id=468108 --- Comment #8 from Jonatan Cloutier --- While working on my document (still with old version) I notice I got a lot of error of this type: * Sum of splits in transaction 'T023881' posted on 2022-10-27 is not zero. Account: Passif:, Amount: (13,79 $) Those are all transaction I haven't yet setted a category which explain the error (although, being notified on every save is a bit annoying, but that's another issue) I have 290 of those error currently, and it might match the accounts that are getting very slow (obviously it's the account with more transaction that take more time for me to properly cleanup) At least two of them are concerned -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 459392] warning: The macro `AC_PROG_CC_C99' is obsolete
https://bugs.kde.org/show_bug.cgi?id=459392 Dustin Hacker changed: What|Removed |Added CC||ldhac...@live.com --- Comment #2 from Dustin Hacker --- I was able to correct this and run autogen.sh completely by changing 'AC_PROG_CC_C99' to 'AC_PROG_CC' in the configure.ac file on the line mentioned by @Ömer Fadıl USTA in comment 1. This is correct in accordance with https://www.gnu.org/savannah-checkouts/gnu/autoconf/manual/autoconf-2.71/html_node/C-Compiler.html#AC_005fPROG_005fCC because AC_PROG_CC replaced the obsolete AC_PROG_CC_C99 autoconf macro. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468264] New: feature request: resource bundle deletion and user feedback
https://bugs.kde.org/show_bug.cgi?id=468264 Bug ID: 468264 Summary: feature request: resource bundle deletion and user feedback Classification: Applications Product: krita Version: 5.1.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Resource Management Assignee: krita-bugs-n...@kde.org Reporter: bobrosspaint...@protonmail.com Target Milestone: --- Hello friends SUMMARY In 'settings' - 'manage resources': there is a button 'import resources' to install a bundle. I like to request 2 things to make this window better for the user. 1. When a bundle is installed by using the 'import resources' button , there is no feedback to the user the installation is finished (also no progress bar of the installation process in the UI). I would like to request a message box saying 'installation finished successfully' and/or a progress bar during installation (big bundle can take some time). 2. I don't find a button to delete a complete bundle. It could be handy, after selecting a bundle using the 'local resources' combobox, to have a button 'delete complete bundle' to remove it completely. Remember: there are no bugs, only happy little accidents! Bob Ross The joy of painting -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 468263] New: bundle brushes not all loaded after installing
https://bugs.kde.org/show_bug.cgi?id=468263 Bug ID: 468263 Summary: bundle brushes not all loaded after installing Classification: Applications Product: krita Version: 5.1.5 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: bobrosspaint...@protonmail.com Target Milestone: --- Hello friends SUMMARY After installing this brush bundle in krita 5.1.5 https://github.com/Rakurri/rakurri-brush-set-for-krita/releases/tag/V2.1 Only 4 brushes where shown in krita. I had to close and open krita again to make them all appear in the docker. I think something is not refreshed after installing a bundle. STEPS TO REPRODUCE 1. Install https://github.com/Rakurri/rakurri-brush-set-for-krita/releases/tag/V2.1 2. See only 4 brushes are in the docker 3. Close and restart krita to see them all appear OBSERVED RESULT Not all brushes are shown EXPECTED RESULT All brushes should be shown without restarting krita Remember: there are no bugs, only happy little accidents! Bob Ross The joy of painting -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 468262] New: Dual-DisplayPort monitor only shows image on half of the screen
https://bugs.kde.org/show_bug.cgi?id=468262 Bug ID: 468262 Summary: Dual-DisplayPort monitor only shows image on half of the screen Classification: Plasma Product: KScreen Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: kde@axhxrx.com Target Milestone: --- Created attachment 157939 --> https://bugs.kde.org/attachment.cgi?id=157939=edit screen shot of malfunction SUMMARY After updating to KDE Plasma 5.27.4, the Dell UP3218K monitor no longer displays an image on the entire screen. Instead, it displays an image in a rectangle that is half the size of the screen. STEPS TO REPRODUCE 1. Upgrade to KDE Plasma 5.27.4 2. Log in using "KDE Plasma (Wayland)" 3. Look at the monitor OBSERVED RESULT The monitor only displays an image within a rectangle that is half of the screen size (photo attached). EXPECTED RESULT The monitor should display an image on the entire display. (This was the result in KDE Plasma 5.27.3, and at least several previous versions.) SOFTWARE/OS VERSIONS Fedora 37 (KDE spin) KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 GPU: amdgpu (AMD RADEON RX 6600) ADDITIONAL INFORMATION This is the Dell UP3128K display, which is one of those older models that uses 2 DisplayPort cables to connect, and although it is a single 8K monitor, it is made up of two 4K panels. The left and right half of the monitor appear as two different screens in the "Display Configuration" pane of the System Settings application. Prior to KDE Plasma 5.27.4, these can be arranged side by side, so the entire display can be used. Windows can be displayed normally, even if the window occupies space on both of the screens. Because the left half and the right half of this monitor are regarded as two different screens, the default panel will by default appear on only one half of the monitor (because it is only supposed to show on one screen), and likewise maximizing a window will cause it to occupy only half of the physical monitor (because zooming only considers a single screen) and so forth. These are normal limitations of using this monitor with most desktop environments. It might be suspected, but is not the case, that the regression under discussion here involves using only one of the two panels in the monitor. In fact, the visual area that the image shows on spans both panels and it centered on the physical monitor. That is, the left (or right, I actually cannot tell) screen that is supposed to be on one panel on one half of the monitor is instead centered, displaying on half of each 4K panel, while the other screen does not appear at all. Disabling one of the two "Dell Inc DELL UP3218K" screens and leaving the other enabled causes the monitor to go black. Reversing that shows an image, so it seems only one of the two screens is actually capable of producing an image on the monitor. REPRODUCTION AND DEBUGGING I confirmed the expected behavior by rolling back the machine in question to the previously-installed OS snapshot, which is Fedora 37 with KDE Plasma 5.27.3 and everything works as expected. I also tested with Fedora 38 beta with GNOME, and it also drives the monitor without a problem. So I believe the monitor and GPU are working correctly. I also tried logging into the KDE Plasma 5.27.4 using X11 instead of Wayland. Although X11 is not very usable in the multi-monitor setup that I normally use, if one ignores the usual X11 jank/freakout thing where it flashes monitors on and off in an apparent hallucinatory fugue state for a considerable period of time, it does eventually drive the displays and show the desktop on them. However, I confirmed that this same regression is present in KDE Plasma 5.27.4 using X11, and is not specific to Wayland. Duplicating this hardware configuration is probably difficult, but I would be happy to help collect diagnostic information or test any potential fixes using the hardware I have. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468261] New: [Colors:Header][Inactive] section missing in KColorSchemeEditor
https://bugs.kde.org/show_bug.cgi?id=468261 Bug ID: 468261 Summary: [Colors:Header][Inactive] section missing in KColorSchemeEditor Classification: Applications Product: systemsettings Version: 5.27.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_colors Assignee: plasma-b...@kde.org Reporter: k...@b-vo.fr CC: noaha...@gmail.com, tantalising...@gmail.com, uhh...@gmail.com Target Milestone: --- Created attachment 157938 --> https://bugs.kde.org/attachment.cgi?id=157938=edit KColorSchemeEditor screenshot SUMMARY It is currently not possible to change the colors of hte [Colors:Header][Inactive] section in KColorSchemeEditor. STEPS TO REPRODUCE 1. Edit a color scheme 2. Pick color set OBSERVED RESULT Header section is available but not the Header[Inactive] EXPECTED RESULT Add Header (inactive) section SOFTWARE/OS VERSIONS Linux/KDE Plasma: NixOS unstable 23.05 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468235] Screen refresh rate stuck at 60hz even when set to 144hz in the display settings
https://bugs.kde.org/show_bug.cgi?id=468235 gfunk changed: What|Removed |Added CC||trist...@posteo.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466346] kwin_wayland crashes in KWaylandServer::OutputInterface::handle() when disabling and re-enabling a screen and letting it get turned off via power management
https://bugs.kde.org/show_bug.cgi?id=466346 --- Comment #18 from Aleix Pol --- This new backtrace looks nothing like the former one. Can you please open a new bug? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461429] Kwin (?) crashes out of nowhere
https://bugs.kde.org/show_bug.cgi?id=461429 --- Comment #11 from André M --- Ok, I managed to get a stacktrace of a "RT throttling activated" frozen kwin_wayland instance. It seems to happen inside `KWin::Placement::placeSmart` function specifically when launching _certain_ wayland windows (maybe my Signal repro just triggered it because I often use it with non-maximized/with some specific remembered geometry?). That function has a very suspicious `do/while` b;pclk, which may be causing an infinite loop here. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468260] New: Regression: "workspace.clientArea(KWin.MaximizeArea, client)" returns wrong values (AKA "Move Window" KWin script broke)
https://bugs.kde.org/show_bug.cgi?id=468260 Bug ID: 468260 Summary: Regression: "workspace.clientArea(KWin.MaximizeArea, client)" returns wrong values (AKA "Move Window" KWin script broke) Classification: I don't know Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: denilso...@gmail.com Target Milestone: --- SUMMARY Since the latest KDE Plasma (5.27.3) was installed on my Manjaro Linux, the "Move Window" KWin script broke (i.e. it's not behaving properly). STEPS TO REPRODUCE 1. Install this KWin script https://store.kde.org/p/1702170/ 2. Go to KDE settings and enable that script. Observe it will map Super+Numpad to actions to move the current window to one of the 9 locations on the current screen (top/middle/bottom + left/middle/right). 3. Have two connected displays, and set then in a way that leaves some unused area. For instance, the left display in the horizontal orientation and the right display in the vertical one: .. || .---|| | || '---'' 4. Focus on any window on the left display (or on either display). 5. Use Super+Numpad shortcuts to move the window. OBSERVED RESULT The window is moved to unexpected locations, places that are definitely not the center. Sometimes the window gets moved off-screen (probably in that unusable area). EXPECTED RESULT I should "just work", as it used to work in the previous KDE versions. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro Linux KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Graphics Plataform: X11 ADDITIONAL INFORMATION This bug has also been reported here: https://github.com/Merrit/kwin-move-window/issues/3 However, I believe the bug is in KDE itself, and not on that KWin script (as that script is unchanged, while KDE got serious updates regarding multi-display setups). -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 467094] Typeset using LaTeX option need to be disabled and enabled again every time
https://bugs.kde.org/show_bug.cgi?id=467094 intrloc...@outlook.com changed: What|Removed |Added CC||intrloc...@outlook.com --- Comment #1 from intrloc...@outlook.com --- Created attachment 157937 --> https://bugs.kde.org/attachment.cgi?id=157937=edit Issue also present on Arch Linux I am additionally facing this issue on Arch Linux, with the same version of Cantor as the reporter and Maxima SBCL version 5.46.0. Attached is the output from running Cantor via a terminal with "Typeset using LaTeX" enabled in settings. No LaTeX output was generated. As an aside, if "Typeset using LaTeX" is disabled in settings but then enabled per worksheet after starting Cantor, rendering works as expected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465444] xwayland firefox tab doesnt appear unless mouse over
https://bugs.kde.org/show_bug.cgi?id=465444 David Edmundson changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/kwin/commit/023fc220a126 ||7876ebb210619672271f8c2130d ||7 Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #8 from David Edmundson --- Git commit 023fc220a1267876ebb210619672271f8c2130d7 by David Edmundson. Committed on 07/04/2023 at 22:14. Pushed by davidedmundson into branch 'master'. wayland: Update pointer state before ending the drag ending a drag will update focus. Kwin explicitly resets it to whatever is now under the mouse now that the implicit grab has ended. This means no-one sends a pointer up. Clients (xwayland) don't automatically make leave events count as a mouse up, because typically you don't get a leave event whilst we have a grab. Xwayland also can't track the status of the wl_datasource as it didn't use it. This patch shouldn't affect any wayland clients as we don't send a frame event until the focus changes which is after the dnd_finished events. Testing done: - dragged firefox under xwayland tabs out from firefox to the desktop - confirmed a new window appeared M +4-2src/wayland/autotests/client/test_drag_drop.cpp M +1-0src/wayland/seat_interface.cpp https://invent.kde.org/plasma/kwin/commit/023fc220a1267876ebb210619672271f8c2130d7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438315] Kwin crashed in KWin::FocusChain::isUsableFocusCandidate()
https://bugs.kde.org/show_bug.cgi?id=438315 --- Comment #8 from David Edmundson --- *** Bug 463434 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463434] When closing certain windows KWin crash
https://bugs.kde.org/show_bug.cgi?id=463434 David Edmundson changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REOPENED|RESOLVED --- Comment #11 from David Edmundson --- *** This bug has been marked as a duplicate of bug 438315 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 431566] msg and call notifications from Android phone are coming all again after disconnecting and later reconnecting the phone
https://bugs.kde.org/show_bug.cgi?id=431566 Albert Vaca changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from Albert Vaca --- This should be fixed now, see #411598 *** This bug has been marked as a duplicate of bug 411598 *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 411598] Quietly sync existing notifications when phone connects
https://bugs.kde.org/show_bug.cgi?id=411598 Albert Vaca changed: What|Removed |Added CC||michael.hm...@gmail.com --- Comment #3 from Albert Vaca --- *** Bug 431566 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412188] Notifications from applications in work profile cannot be disabled
https://bugs.kde.org/show_bug.cgi?id=412188 --- Comment #1 from Albert Vaca --- Indeed this is lacking and we should add the option to either disable work notifications completely or app-by-app (or both). -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 412188] Notifications from applications in work profile cannot be disabled
https://bugs.kde.org/show_bug.cgi?id=412188 Albert Vaca changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 468217] xf86-input-libinput 1.3.0 DPI and mouse acceleration issue on KDE Plasma X11
https://bugs.kde.org/show_bug.cgi?id=468217 pmw...@protonmail.ch changed: What|Removed |Added CC||pmw...@protonmail.ch -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 411598] Quietly sync existing notifications when phone connects
https://bugs.kde.org/show_bug.cgi?id=411598 Albert Vaca changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Albert Vaca --- This has been fixed in https://invent.kde.org/network/kdeconnect-android/-/merge_requests/330 and will be released in the upcoming Android version. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 468259] High CPU usage during intensive scrolling
https://bugs.kde.org/show_bug.cgi?id=468259 --- Comment #1 from Yaroslav --- I can repro the same issue with qterminal , but with smaller performance hit (CPU usage hovers in 20% to 50%, which is still too much compared with VTE-based terminals). Highest CPU consumer is the same (alphargbblend_argb32 ) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 458487] Share Plugin: URLs with titles should be shared as plain URLs
https://bugs.kde.org/show_bug.cgi?id=458487 Albert Vaca changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED --- Comment #3 from Albert Vaca --- In the end we decided to still share the URL with the text and then on the desktop side offer the option to open the link or copy the text up to the user. This was implemented in: https://invent.kde.org/network/kdeconnect-kde/-/merge_requests/530 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 468259] New: High CPU usage during intensive scrolling
https://bugs.kde.org/show_bug.cgi?id=468259 Bug ID: 468259 Summary: High CPU usage during intensive scrolling Classification: Applications Product: konsole Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: yaroslav.rastri...@gmail.com Target Milestone: --- SUMMARY *** scrolling a lot of text incurs large performance overhead. konsole is consuming up to 65% of a single core if I'm doing, f.e. , `tail` -f of a quickly updating log file *** STEPS TO REPRODUCE 1. induce scrolling . easiest way is to run 'while [ 1 ] ; do echo 'testtesttesttesttest' ; done 2. open `top` or run another performance monitor OBSERVED RESULT high cpu usage, over 50% of a single core EXPECTED RESULT negligible cpu usage, as with other terminal emulation software SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: kde-frameworks/plasma-5.104.0:5/5.104 KDE Frameworks Version: 5.104 Qt Version: 5.15.8 ADDITIONAL INFORMATION I have tested this with both Gentoo packages built from source by myself , and precompiled Arch linux packages. During investigation I've compiled konsole and QtGui with debugging symbols, and ran `perf record` + `perf report` dwhile reproducing the issue. The culprit seems to be incorrect or excessive usage of alphargbblend_argb32 37.13% 0.00% konsole libQt5Gui.so.5.15.8 [.] QtSharedPointer::ExternalRefCountWithCustomDeleter::deleter | ---QtSharedPointer::ExternalRefCountWithCustomDeleter::deleter 0x5645ea71a9c0 | |--31.87%--alphargbblend_argb32 | --5.26%--qt_alphargbblit_argb32 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 419998] tracks from gpx lines are painted as a px white line, invisible almost
https://bugs.kde.org/show_bug.cgi?id=419998 --- Comment #7 from Axel Braun --- (In reply to Torsten Rahn from comment #6) > Sorry that this took so embarrassing long. A fix in 3 years is clearly above average in KDE... SCNR, and highly frustrated! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434057] Add stdio mode to valgrind's gdbserver
https://bugs.kde.org/show_bug.cgi?id=434057 --- Comment #17 from Paul Floyd --- I'll have a go over the weekend. -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 433859] Add mismatched detection to C++ 17 aligned new/delete
https://bugs.kde.org/show_bug.cgi?id=433859 Paul Floyd changed: What|Removed |Added Attachment #157921|0 |1 is obsolete|| -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 433859] Add mismatched detection to C++ 17 aligned new/delete
https://bugs.kde.org/show_bug.cgi?id=433859 --- Comment #11 from Paul Floyd --- Created attachment 157936 --> https://bugs.kde.org/attachment.cgi?id=157936=edit Big patch for lots of aligned / sized alloc errors Last macOS and doc changes -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449141] Polish loop in a ListView sometimes causes Kickoff to hang
https://bugs.kde.org/show_bug.cgi?id=449141 --- Comment #27 from patrick.winter...@t-online.de --- That's something to look forward to then, thanks for the tip. -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 466853] Marble crashes on exit.
https://bugs.kde.org/show_bug.cgi?id=466853 --- Comment #3 from Rick Smegal --- How does one execute marble with the marble-qt front end installed? The only executable I see is: /usr/bin/marble-qt On 2023-04-07 12:56, Torsten Rahn wrote: > https://bugs.kde.org/show_bug.cgi?id=466853 > > Torsten Rahn changed: > > What|Removed |Added > > CC||r...@kde.org > > --- Comment #2 from Torsten Rahn --- > So does the issue still occur with "marble" but not with "marble-qt" ? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 452852] Plasmashell runs at 100% CPU and freezes when #449141 occurs
https://bugs.kde.org/show_bug.cgi?id=452852 postix changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=449141| -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449141] Polish loop in a ListView sometimes causes Kickoff to hang
https://bugs.kde.org/show_bug.cgi?id=449141 postix changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=452852| --- Comment #26 from postix --- FWIW, I couldn't observe this bug since plasma 5.25? 5.26? and definitely no longer in 5.27. (In reply to patrick.wintering from comment #25) > OpenSUSE Leap 15.4 with KDE Plasma 5.24.4, Frameworks 5.90.0, Qt 5.15.2 Leap 15.5 beta is currently running. Once it comes out, it should offer a recent Plasma version [1], where the bug should be fixed. [1] https://build.opensuse.org/package/show/openSUSE:Leap:15.5:Update/kwin5 -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 466220] App crashes when starting, no download from google playstore
https://bugs.kde.org/show_bug.cgi?id=466220 Torsten Rahn changed: What|Removed |Added CC||r...@kde.org --- Comment #1 from Torsten Rahn --- I'm working on getting Marble out of its current "hibernation status". We're Open again. Stay tuned :-) -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 466853] Marble crashes on exit.
https://bugs.kde.org/show_bug.cgi?id=466853 Torsten Rahn changed: What|Removed |Added CC||r...@kde.org --- Comment #2 from Torsten Rahn --- So does the issue still occur with "marble" but not with "marble-qt" ? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 468036] Form: NaN in form total (UK IHT 411)
https://bugs.kde.org/show_bug.cgi?id=468036 Dave Gilbert changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #4 from Dave Gilbert --- OK, fix incoming; it's just that we're missing a definition of valueAsString -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 449141] Polish loop in a ListView sometimes causes Kickoff to hang
https://bugs.kde.org/show_bug.cgi?id=449141 patrick.winter...@t-online.de changed: What|Removed |Added CC||patrick.wintering@t-online. ||de --- Comment #25 from patrick.winter...@t-online.de --- OpenSUSE Leap 15.4 with KDE Plasma 5.24.4, Frameworks 5.90.0, Qt 5.15.2 In my case searching "term" breaks kickoff into the same endless loop as mentioned in the initial comment. It will not always break, but usually. I've discovered that disabling the applications plugin stops the loop from happening when I search "term". Of course I can't say if the issue is actually in that plugin or if it just triggers a bug in Kickoff. Unfortunately Kickoff without the applications plugin is fairly useless... In case anyone needed a visual example on what's happening I've uploaded an example video here: https://youtu.be/ZoGRwOctXDc -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 423232] option to disable pdf preview
https://bugs.kde.org/show_bug.cgi?id=423232 witchhunter changed: What|Removed |Added CC||witchhunterpro@protonmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 437062] Glitch on hover over context menu of a window decoration on Wayland when using non-opaque menu with blur effect
https://bugs.kde.org/show_bug.cgi?id=437062 --- Comment #18 from postix --- Is this bug by any chance also fixed with https://bugreports.qt.io/browse/QTBUG-93380 ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432264] In multi-monitor setups with differenlty scaled displays, Context menus have items which are invisible until hovered
https://bugs.kde.org/show_bug.cgi?id=432264 postix changed: What|Removed |Added Version Fixed In||Qt 6.6 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 437062] Glitch on hover over context menu of a window decoration on Wayland when using non-opaque menu with blur effect
https://bugs.kde.org/show_bug.cgi?id=437062 postix changed: What|Removed |Added Version|5.21.90 |5.27.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438198] In wayland moving a window to another desktop becomes a needlessly complicated task
https://bugs.kde.org/show_bug.cgi?id=438198 postix changed: What|Removed |Added Status|CONFIRMED |NEEDSINFO Resolution|--- |WAITINGFORINFO CC||pos...@posteo.eu --- Comment #4 from postix --- Can you still reproduce this bug with a more recent version? -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468203] GTK3 window buttons are too big and blurry on Wayland with Breeze GTK
https://bugs.kde.org/show_bug.cgi?id=468203 --- Comment #22 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/breeze-gtk/-/merge_requests/81 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454779] QMenus mispositioned using Wayland QPA with multiple monitors when top edges of monitors are not aligned
https://bugs.kde.org/show_bug.cgi?id=454779 postix changed: What|Removed |Added CC||pos...@posteo.eu --- Comment #6 from postix --- (In reply to Be from comment #4) > Ping David, could you link to that upstream Qt bug? (In reply to Nicolas Fella from comment #3) > > there's a qt bug upstream > > Can you link that here? I assume it's this one: https://bugreports.qt.io/browse/QTBUG-85297 ? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 455609] Context menu position
https://bugs.kde.org/show_bug.cgi?id=455609 postix changed: What|Removed |Added CC||pos...@posteo.eu Resolution|UPSTREAM|DUPLICATE --- Comment #2 from postix --- *** This bug has been marked as a duplicate of bug 454779 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 454779] QMenus mispositioned using Wayland QPA with multiple monitors when top edges of monitors are not aligned
https://bugs.kde.org/show_bug.cgi?id=454779 postix changed: What|Removed |Added CC||chni...@gmail.com --- Comment #5 from postix --- *** Bug 455609 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 418868] Notifier shows X11 icon instead of Notifier icon in title bar
https://bugs.kde.org/show_bug.cgi?id=418868 postix changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 419998] tracks from gpx lines are painted as a px white line, invisible almost
https://bugs.kde.org/show_bug.cgi?id=419998 Torsten Rahn changed: What|Removed |Added CC||r...@kde.org Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #6 from Torsten Rahn --- Sorry that this took so embarrassing long. Fixed with: commit fbb2d704c615a1cd4968bed49a0d4b26c1469134 (origin/master, origin/HEAD) Author: Anthony P. Austin Date: Sun Jul 24 10:46:22 2022 -0700 Restore former GPX rendering behavior. Previous versions of Marble rendered GPX tracks using a thick red line and then recentered and zoomed the map so that the newly-loaded track occupied most of the display. At some point, this behavior got lost; for some time now, Marble has been rendering GPX tracks as a difficult-to-see 1-pixel-wide white line and not recentering or zooming the map, leading some users to the conclusion that the software wasn't loading the track at all. See the following bug reports: https://bugs.kde.org/show_bug.cgi?id=419998 https://bugs.kde.org/show_bug.cgi?id=411669 https://bugs.kde.org/show_bug.cgi?id=370263 https://bugs.kde.org/show_bug.cgi?id=402153 This patch restores the old rendering behavior. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466346] kwin_wayland crashes in KWaylandServer::OutputInterface::handle() when disabling and re-enabling a screen and letting it get turned off via power management
https://bugs.kde.org/show_bug.cgi?id=466346 Antonio Rojas changed: What|Removed |Added CC|aro...@archlinux.org| -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468258] PyCharm's code completion window is not usable on Wayland using dual screen setup with mixed scaling and primary on the right + kwin freezes
https://bugs.kde.org/show_bug.cgi?id=468258 postix changed: What|Removed |Added Version|unspecified |5.27.3 Keywords||wayland Platform|Other |openSUSE -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468258] PyCharm's code completion window is not usable on Wayland using dual screen setup with mixed scaling and primary on the right + kwin freezes
https://bugs.kde.org/show_bug.cgi?id=468258 --- Comment #4 from postix --- Last but not least, PyCharm runs under xwayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468258] PyCharm's code completion window is not usable on Wayland using dual screen setup with mixed scaling and primary on the right + kwin freezes
https://bugs.kde.org/show_bug.cgi?id=468258 --- Comment #3 from postix --- Created attachment 157935 --> https://bugs.kde.org/attachment.cgi?id=157935=edit journalctl log -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468258] PyCharm's code completion window is not usable on Wayland using dual screen setup with mixed scaling and primary on the right + kwin freezes
https://bugs.kde.org/show_bug.cgi?id=468258 --- Comment #2 from postix --- Created attachment 157934 --> https://bugs.kde.org/attachment.cgi?id=157934=edit Screenshot of the 2nd screen This screenshot shows the `code completion window` how it appears at some point in time in the upper left corner of the left 2k@100% non-primary screen. It scales like 0.5. This bug is also reproducible if `Scaling by the system` is set in kscreen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468258] PyCharm's code completion window is not usable on Wayland using dual screen setup with mixed scaling and primary on the right + kwin freezes
https://bugs.kde.org/show_bug.cgi?id=468258 --- Comment #1 from postix --- Created attachment 157933 --> https://bugs.kde.org/attachment.cgi?id=157933=edit kWin Support Info -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468258] New: PyCharm's code completion window is not usable on Wayland using dual screen setup with mixed scaling and primary on the right + kwin freezes
https://bugs.kde.org/show_bug.cgi?id=468258 Bug ID: 468258 Summary: PyCharm's code completion window is not usable on Wayland using dual screen setup with mixed scaling and primary on the right + kwin freezes Classification: Plasma Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- Created attachment 157932 --> https://bugs.kde.org/attachment.cgi?id=157932=edit Screen recording SUMMARY When entering some code in the IDE, the code completion window pops up. However, while typing this window flashes at random positions with random scaling and size and sometimes appears just as a black rectangle for fraction of a second. Even worse, it can make the compositor completely freeze for a minute or so, where even keyboard or mouse input stops working. You can notice that the compositor first slows down while typing as there's a certain input lag until it becomes fully unresponsive. Journalctl had logged the following (1085 times, i.e. 22 events per second): > 19:19:22 kwin_wayland_wrapper[2179]: Key repeat discarded, Wayland compositor > doesn't seem to be processing events fast enough! as well as > 19:19:22 kwin_wayland[2127]: kwin_core: XCB error: 3 (BadWindow), sequence: > 52994, resource id: 18926880, major code: 129 (SHAPE), minor code: 3 (Combine) When it finally had cooled down again, instead of an `else` I had `el()ll` with roughly 1400 `l`s in the code input area. This seems to be a regression as I definitely could not observe these issues in 5.26 or prior. STEPS TO REPRODUCE 1) Dual screen: 2k@100% on the left, 4k@200% on the right + primary I could not observe it with any other constellations so far. Unfortunately this is the setup I currently got to work with. 2) Please see the attached screen recording. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230404 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.9-1-default (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.2 GiB of RAM Graphics Processor: AMD Radeon RX 580 Series PyCharm 2023.1 (Professional Edition) Build #PY-231.8109.197, built on March 29, 2023 Runtime version: 17.0.6+10-b829.5 amd64 VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 450317] Items sometimes overlap if there are many items
https://bugs.kde.org/show_bug.cgi?id=450317 postix changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #15 from postix --- I couldn't observe this anymore since 5.27.3. I guess and hope the issue gone forever. Therefore I close it for now. ;) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466346] kwin_wayland crashes in KWaylandServer::OutputInterface::handle() when disabling and re-enabling a screen and letting it get turned off via power management
https://bugs.kde.org/show_bug.cgi?id=466346 kfsbgd4o4...@opayq.com changed: What|Removed |Added Version|5.27.3 |5.27.4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466346] kwin_wayland crashes in KWaylandServer::OutputInterface::handle() when disabling and re-enabling a screen and letting it get turned off via power management
https://bugs.kde.org/show_bug.cgi?id=466346 --- Comment #17 from kfsbgd4o4...@opayq.com --- Created attachment 157931 --> https://bugs.kde.org/attachment.cgi?id=157931=edit kwin_wayland stack trace -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466346] kwin_wayland crashes in KWaylandServer::OutputInterface::handle() when disabling and re-enabling a screen and letting it get turned off via power management
https://bugs.kde.org/show_bug.cgi?id=466346 kfsbgd4o4...@opayq.com changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #16 from kfsbgd4o4...@opayq.com --- Still experiencing crash on 5.27.4 Stack trace of thread 1348: #0 0x7efd2b9b56f3 _ZN4KWin12DrmGammaRampC2EPNS_7DrmCrtcERKSt10shared_ptrINS_19ColorTransformationEE (libkwin.so.5 + 0x3b56f3) #1 0x7efd2b9b5dd8 _ZN4KWin9DrmOutput12setGammaRampERKSt10shared_ptrINS_19ColorTransformationEE (libkwin.so.5 + 0x3b5dd8) #2 0x7efd2b7eea0a _ZN4KWin11ColorDevice6updateEv (libkwin.so.5 + 0x1eea0a) #3 0x7efd29ed0e96 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d0e96) #4 0x7efd2b7f9731 _ZN4KWin6Output8setStateERKNS0_5StateE (libkwin.so.5 + 0x1f9731) #5 0x7efd2b9aac99 _ZN4KWin9DrmOutput14updateDpmsModeENS_6Output8DpmsModeE (libkwin.so.5 + 0x3aac99) #6 0x7efd2b9abd8d _ZN4KWin9DrmOutput14setDrmDpmsModeENS_6Output8DpmsModeE (libkwin.so.5 + 0x3abd8d) #7 0x7efd2b9abfb6 _ZN4KWin9DrmOutput11setDpmsModeENS_6Output8DpmsModeE (libkwin.so.5 + 0x3abfb6) #8 0x7efd2b98573b _ZN4KWin10DrmBackend13turnOutputsOnEv (libkwin.so.5 + 0x38573b) #9 0x7efd2b9b4af0 _ZN4KWin9DrmOutput18applyQueuedChangesERKNS_19OutputConfigurationE (libkwin.so.5 + 0x3b4af0) #10 0x7efd2b98dccf _ZN4KWin10DrmBackend18applyOutputChangesERKNS_19OutputConfigurationE (libkwin.so.5 + 0x38dccf) #11 0x7efd2b938a45 _ZN4KWin9Workspace24applyOutputConfigurationERKNS_19OutputConfigurationERK7QVectorIPNS_6OutputEE (libkwin.so.5 + 0x338a45) #12 0x7efd2ba0d7da _ZN14KWaylandServer30OutputConfigurationV2Interface33kde_output_configuration_v2_applyEPN15QtWaylandServer27kde_output_configuration_v28ResourceE (libkwin.so.5 + 0x40d7da) #13 0x7efd270e3a06 ffi_call_unix64 (libffi.so.8 + 0x7a06) #14 0x7efd270e049d ffi_call_int.lto_priv.0 (libffi.so.8 + 0x449d) #15 0x7efd270e3083 ffi_call (libffi.so.8 + 0x7083) #16 0x7efd286b5728 wl_closure_invoke.constprop.0 (libwayland-server.so.0 + 0x9728) #17 0x7efd286b9ac8 wl_client_connection_data (libwayland-server.so.0 + 0xdac8) #18 0x7efd286b8532 wl_event_loop_dispatch (libwayland-server.so.0 + 0xc532) #19 0x7efd2b9ee186 _ZN14KWaylandServer7Display14dispatchEventsEv (libkwin.so.5 + 0x3ee186) #20 0x7efd29ed0e96 _Z10doActivateILb0EEvP7QObjectiPPv (libQt5Core.so.5 + 0x2d0e96) #21 0x7efd29ed3703 _ZN15QSocketNotifier9activatedE17QSocketDescriptorNS_4TypeENS_14QPrivateSignalE (libQt5Core.so.5 + 0x2d3703) #22 0x7efd29ed3f25 _ZN15QSocketNotifier5eventEP6QEvent (libQt5Core.so.5 + 0x2d3f25) #23 0x7efd295aed62 _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt5Widgets.so.5 + 0x1aed62) #24 0x7efd29e9d4e8 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt5Core.so.5 + 0x29d4e8) #25 0x7efd29eeba8e _ZN27QEventDispatcherUNIXPrivate23activateSocketNotifiersEv (libQt5Core.so.5 + 0x2eba8e) #26 0x7efd29eebecd _ZN20QEventDispatcherUNIX13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt5Core.so.5 + 0x2ebecd) #27 0x558a0d4f15c1 _ZN23QUnixEventDispatcherQPA13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (kwin_wayland + 0x13b5c1) #28 0x7efd29e9bf3a _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt5Core.so.5 + 0x29bf3a) #29 0x7efd29ea4002 _ZN16QCoreApplication4execEv (libQt5Core.so.5 + 0x2a4002) #30 0x558a0d411d21 main (kwin_wayland + 0x5bd21) #31 0x7efd28e4a510 __libc_start_call_main (libc.so.6 + 0x27510) #32 0x7efd28e4a5c9 __libc_start_main@@GLIBC_2.34 (libc.so.6 + 0x275c9) #33 0x558a0d413885 _start (kwin_wayland + 0x5d885) Operating System: Fedora Linux 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.9-200.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800H with Radeon Graphics Memory: 13.5 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 82MS System Version: Lenovo XiaoXinPro 14ACH 2021 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468235] Screen refresh rate stuck at 60hz even when set to 144hz in the display settings
https://bugs.kde.org/show_bug.cgi?id=468235 tju...@gmail.com changed: What|Removed |Added CC||tju...@gmail.com --- Comment #2 from tju...@gmail.com --- I have the same problem with a Gigabyte FI32Q monitor, I'm also on Archlinux and the problem started when I upgraded to 5.27.4. On my monitor it's 170Hz that works, on all others (120,144,165) the fps meter on my monitor and the kde one under desktop effects shows 60 fps. Powering off and on the monitor also fixes the problem on my system. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468203] GTK3 window buttons are too big and blurry on Wayland with Breeze GTK
https://bugs.kde.org/show_bug.cgi?id=468203
--- Comment #21 from Fushan Wen ---
For anyone interested, I think this is still a bug in GTK3(Wayland only) and
GTK4. See `gtk_css_image_surface_draw` for example, image_width and
image_height are hardcoded values (For GTK3 it's 18 on Wayland, 50 on X11),
which means when the size of a background image exceeds 18x18 on Wayland, it
will be blurry.
```
static void
gtk_css_image_surface_draw (GtkCssImage *image,
cairo_t *cr,
double width,
double height)
{
GtkCssImageSurface *surface = GTK_CSS_IMAGE_SURFACE (image);
int image_width, image_height;
image_width = cairo_image_surface_get_width (surface->surface);
image_height = cairo_image_surface_get_height (surface->surface);
if (image_width == 0 || image_height == 0 || width <= 0 || height <= 0)
return;
/* Update cache image if size is different */
if (surface->cache == NULL ||
ABS (width - surface->width) > 0.001 ||
ABS (height - surface->height) > 0.001)
{
double xscale, yscale;
cairo_t *cache;
/* We need the device scale (HiDPI mode) to calculate the proper size in
* pixels for the image surface and set the cache device scale
*/
cairo_surface_get_device_scale (cairo_get_target (cr), , );
/* Save original size to preserve precision */
surface->width = width;
surface->height = height;
/* Destroy old cache if any */
g_clear_pointer (>cache, cairo_surface_destroy);
/* Image big enough to contain scaled image with subpixel precision */
surface->cache = cairo_surface_create_similar_image (surface->surface,
CAIRO_FORMAT_ARGB32,
ceil (width*xscale),
ceil
(height*yscale));
cairo_surface_set_device_scale (surface->cache, xscale, yscale);
cache = cairo_create (surface->cache);
cairo_rectangle (cache, 0, 0, width, height);
cairo_scale (cache, width / image_width, height / image_height);
cairo_set_source_surface (cache, surface->surface, 0, 0);
cairo_fill (cache);
cairo_destroy (cache);
}
cairo_rectangle (cr, 0, 0, width, height);
cairo_set_source_surface (cr, surface->cache ? surface->cache :
surface->surface, 0, 0);
cairo_fill (cr);
}
```
--
You are receiving this mail because:
You are watching all bug changes.
[systemsettings] [Bug 421745] On Wayland, the color scheme of gtk3 apps is not immediately updated when I change the global theme; the apps need to be restarted
https://bugs.kde.org/show_bug.cgi?id=421745 --- Comment #45 from SoilpH96 --- For me, the GTK color settings aren't applied the first time after I open a application if I use the plasma-apply-colorscheme command line tool (both when using it directly or invoking it from scripts). They will be applied at all subsequent times, and will be applied if the color scheme is changed from System Settings. Firefox also does not apply the color scheme correctly the first time even if using System Settings, appearing to use the Adwaita theme, but will apply it correctly at subsequent times. Chromium appears to require restarting to apply any color scheme correctly. The end result is that currently theme switching automated via scripting remains mostly broken in GTK applications on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468203] GTK3 window buttons are too big and blurry on Wayland with Breeze GTK
https://bugs.kde.org/show_bug.cgi?id=468203 Benjamin Xiao changed: What|Removed |Added CC||ben.r.x...@gmail.com --- Comment #20 from Benjamin Xiao --- I can reproduce this issue on X11 as well on 100% scaling. Both Firefox and Pamac show this issue, except on Firefox it actually looks blurry whereas in Pamac (which I believe is a native GTK app) does proper scaling. Does screen size matter in this case for reproducibility? I have a 4k screen. Arch Linux Plasma 5.27.4 Frameworks 5.104.0 Qt 5.15.8 Nvidia 3090 w/ 530.41.03 drivers -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 458066] Sound icon is not available for flatpak apps
https://bugs.kde.org/show_bug.cgi?id=458066 Patrick Silva changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #9 from Patrick Silva --- Cannot reproduce too. Operating System: Arch Linux KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 468249] Q4OS system settings is broken
https://bugs.kde.org/show_bug.cgi?id=468249 Antonio Rojas changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Antonio Rojas --- The crash is in the Deepin style -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468203] GTK3 window buttons are too big and blurry on Wayland with Breeze GTK
https://bugs.kde.org/show_bug.cgi?id=468203 breakingsp...@gmail.com changed: What|Removed |Added CC||breakingsp...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468257] New: Maximizing then tiling a window, causes it to show stale stretched contents when other windows are maximized or unmaximized
https://bugs.kde.org/show_bug.cgi?id=468257 Bug ID: 468257 Summary: Maximizing then tiling a window, causes it to show stale stretched contents when other windows are maximized or unmaximized Classification: Plasma Product: kwin Version: 5.27.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: compositing Assignee: kwin-bugs-n...@kde.org Reporter: nyanpas...@tuta.io Target Milestone: --- SUMMARY Some windows will enter a state where they show normal contents initially, but the animations to maximize/unmaximize other windows cause them to show stale contents. STEPS TO REPRODUCE 1. Maximize nearly any window (browsers, Qt5, GTK3/4 apps work, glxgears works, xterm doesn't). 2. Use Super+Arrow to tile it to half the screen, without an animation. a. You can stack Super+Up+Left to tile it to a quarter screen, or Super+Left+Left to unmaximize the window without an animation. 3. Maximize or minimize any other window. OBSERVED RESULT The first window (which you tiled out of maximize) shows stale contents from the last time it was maximized, for the duration of the second window's (un/)maximize animation. Sometimes part of the window remains stale after the animation completes. When no animation is playing, you can interact with the stale window's contents normally. But if you maximize another window again, the contents revert to the same stale texture. EXPECTED RESULT Windows do not show corrupted contents when un/maximizing other windows. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.9-zen1-1-zen (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600X 6-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 570 Series Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B550M DS3H ADDITIONAL INFORMATION Unsure if related to Bug 450301? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 468256] New: inconsistent search results for newer files in Dolphin: OK from "My files", empty from specific folder
https://bugs.kde.org/show_bug.cgi?id=468256
Bug ID: 468256
Summary: inconsistent search results for newer files in
Dolphin: OK from "My files", empty from specific
folder
Classification: Applications
Product: dolphin
Version: 22.04.3
Platform: Kubuntu
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: search
Assignee: dolphin-bugs-n...@kde.org
Reporter: brazzmon...@online.fr
CC: kfm-de...@kde.org
Target Milestone: ---
SUMMARY
Search features in Dolphin is inconsistent.
When new files are added into new folders, the do not appear in Dolphin search
results from these newer folders ("from here").
STEPS TO REPRODUCE
1. in Dolphin, create new folders, subfolders
2. in Dolphin, put new files in these newly created folders (JPG files for
instance)
3. in Dolphin, launch search box using 'Ctrl+F', search location "from here"
for files named '*.jpg'
OBSERVED RESULT
No files matching search criteria found.
EXPECTED RESULT
Files matching search criteria listed as results.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Kubuntu 22.04, KDE Plasma 5.25.5
KDE Plasma Version: 5.25.5
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.3
ADDITIONAL INFORMATION
- Baloo indexing seems to be working fine, as 'balooctl monitor' detects new
files and indexes them.
- When "your files" is selected as a search location instead of "from here",
the newest files do appear in search results as expected (but among the many
other files from other folders complying to search criteria...).
- When the same search is done later (I'm talking several hours at least, maybe
days), search results are consistent even using "from here" location.
--
You are receiving this mail because:
You are watching all bug changes.
[ghostwriter] [Bug 468255] New: Cannot build: Qt5LinguistTools is missing
https://bugs.kde.org/show_bug.cgi?id=468255 Bug ID: 468255 Summary: Cannot build: Qt5LinguistTools is missing Classification: Applications Product: ghostwriter Version: unspecified Platform: Debian testing OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: megan.con...@kdemail.net Reporter: prsunflo...@disroot.org Target Milestone: --- SUMMARY Hello fellow community :slightly_smiling_face: I am building Ghostwriter from source but when running **cmake** it runs into an error saying "Could not find a package configuration file provided by "Qt5LinguistTools"". STEPS TO REPRODUCE 1. I have followed the steps to "have the necessary packages installed for Qt 5 and KDE Frameworks" 2. The command "`cmake ..`" runs into a fatal error so I cannot continue OBSERVED RESULT ``` user@PC:~/Builds/ghostwriter/build$ cmake .. -- The CXX compiler identification is GNU 12.2.0 -- Detecting CXX compiler ABI info -- Detecting CXX compiler ABI info - done -- Check for working CXX compiler: /usr/bin/c++ - skipped -- Detecting CXX compile features -- Detecting CXX compile features - done -- Installing in the same prefix as Qt, adopting their path scheme. -- Setting build type to 'Debug' as none was specified. -- Looking for __GLIBC__ -- Looking for __GLIBC__ - found -- Performing Test _OFFT_IS_64BIT -- Performing Test _OFFT_IS_64BIT - Success -- Performing Test HAVE_DATE_TIME -- Performing Test HAVE_DATE_TIME - Success CMake Error at /usr/share/ECM/modules/ECMPoQmTools.cmake:149 (find_package): Could not find a package configuration file provided by "Qt5LinguistTools" with any of the following names: Qt5LinguistToolsConfig.cmake qt5linguisttools-config.cmake Add the installation prefix of "Qt5LinguistTools" to CMAKE_PREFIX_PATH or set "Qt5LinguistTools_DIR" to a directory containing one of the above files. If "Qt5LinguistTools" provides a separate development package or SDK, be sure it has been installed. Call Stack (most recent call first): /usr/share/ECM/modules/ECMPoQmTools.cmake:242 (ecm_process_po_files_as_qm) CMakeLists.txt:46 (ecm_install_po_files_as_qm) -- Configuring incomplete, errors occurred! See also "/home/user/Builds/ghostwriter/build/CMakeFiles/CMakeOutput.log". ``` EXPECTED RESULT No errors, so I can continue with `make` and `make install`. SOFTWARE/OS VERSIONS Linux **Debian Testing**, currently on 12 'bookworm' Qt Version: Qt5? (I followed the instructions to build ghostwriter) ADDITIONAL INFORMATION I would be grateful if someone could assist me :slightly_smiling_face: -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 466373] Qt apps don't use wp-fractional-scale-v1 for hidpi fractional scaling on Wayland
https://bugs.kde.org/show_bug.cgi?id=466373 --- Comment #13 from Dobroslaw Kijowski --- 1) I've backported https://codereview.qt-project.org/c/qt/qtbase/+/447074 to https://github.com/dobo90/qtbase/tree/kde/5.15_fractional_scaling 2) I've cherry-picked https://invent.kde.org/frameworks/qqc2-desktop-style/-/merge_requests/206 to https://github.com/dobo90/qqc2-desktop-style/tree/fractional_scaling 3) I've cherry-picked https://codereview.qt-project.org/c/qt/qtdeclarative/+/447075 to https://github.com/dobo90/qtdeclarative/tree/kde/5.15_fractional_scaling (I don't know if it's need but I've found it on Gerrit). The result is that after opening systemsettings, text on each control is pixelated. But after changing the setting page by clicking on any item, text on most of the controls is rendered properly. I will try to do some digging but my knowledge is very limited in that matter. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468203] GTK3 window buttons are too big and blurry on Wayland with Breeze GTK
https://bugs.kde.org/show_bug.cgi?id=468203 --- Comment #19 from Fushan Wen --- Git commit f9f88c5336063ba853190f790a5c8347afa49afb by Fushan Wen. Committed on 07/04/2023 at 16:36. Pushed by fusionfuture into branch 'master'. kcm: notify changes in kcmfonts when global scale changes Otherwise kde-gtk-config will use the old font DPI value. (cherry picked from commit e9384150d8e41dd9c869f5f502e02c70a5c6f002) M +2-2kcm/kcm.cpp https://invent.kde.org/plasma/kscreen/commit/f9f88c5336063ba853190f790a5c8347afa49afb -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468203] GTK3 window buttons are too big and blurry on Wayland with Breeze GTK
https://bugs.kde.org/show_bug.cgi?id=468203 --- Comment #18 from Fushan Wen --- Git commit 533e397b2dc331d475db0b2c22c085dea70e93d7 by Fushan Wen. Committed on 07/04/2023 at 16:37. Pushed by fusionfuture into branch 'master'. kded: don't update text scale on kdeglobals change events setTextScale() will be called in onKCMFontsSettingsChange (cherry picked from commit 52eb9d01b94eeece64044c5159d965eec7f39079) M +1-1kded/gtkconfig.cpp https://invent.kde.org/plasma/kde-gtk-config/commit/533e397b2dc331d475db0b2c22c085dea70e93d7 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467185] Add Descriptions to Advanced Settings Where Possible
https://bugs.kde.org/show_bug.cgi?id=467185 ratijas changed: What|Removed |Added Status|NEEDSINFO |CONFIRMED Resolution|WAITINGFORINFO |--- --- Comment #4 from ratijas --- Should be easily possible. The rows are Kirigami.BasicListItem, there is a subtitle property in addition to the regular text. As alwaysand since I am not a native speakers, suggestions welcome :) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 468254] New: option to disable clipboard-action-menu during fullscreen
https://bugs.kde.org/show_bug.cgi?id=468254 Bug ID: 468254 Summary: option to disable clipboard-action-menu during fullscreen Classification: Plasma Product: plasmashell Version: master Platform: Neon OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: m.w...@web.de Target Milestone: 1.0 I am using KDE Connect which keeps exchanging clipboards between devices. This triggers the KDE clipboard action menu on the other device. Normally, this is a desired behavior. But it is not desired while playing full screen stuff on the device. Therefor, I wish an option to disable the action menu (or at the least open it in background) while an app is full screen. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468203] GTK3 window buttons are too big and blurry on Wayland with Breeze GTK
https://bugs.kde.org/show_bug.cgi?id=468203 --- Comment #17 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kscreen/-/merge_requests/201 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468203] GTK3 window buttons are too big and blurry on Wayland with Breeze GTK
https://bugs.kde.org/show_bug.cgi?id=468203 --- Comment #16 from Fushan Wen --- Git commit 52eb9d01b94eeece64044c5159d965eec7f39079 by Fushan Wen. Committed on 07/04/2023 at 16:30. Pushed by fusionfuture into branch 'Plasma/5.27'. kded: don't update text scale on kdeglobals change events setTextScale() will be called in onKCMFontsSettingsChange M +1-1kded/gtkconfig.cpp https://invent.kde.org/plasma/kde-gtk-config/commit/52eb9d01b94eeece64044c5159d965eec7f39079 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 468203] GTK3 window buttons are too big and blurry on Wayland with Breeze GTK
https://bugs.kde.org/show_bug.cgi?id=468203 --- Comment #15 from Fushan Wen --- Git commit e9384150d8e41dd9c869f5f502e02c70a5c6f002 by Fushan Wen. Committed on 07/04/2023 at 16:33. Pushed by fusionfuture into branch 'Plasma/5.27'. kcm: notify changes in kcmfonts when global scale changes Otherwise kde-gtk-config will use the old font DPI value. M +2-2kcm/kcm.cpp https://invent.kde.org/plasma/kscreen/commit/e9384150d8e41dd9c869f5f502e02c70a5c6f002 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 464530] Plasma shell freezes when cycling through task manager when window previews are being shown (hover or on grouped)
https://bugs.kde.org/show_bug.cgi?id=464530 --- Comment #13 from Marcelo Bossoni --- Still happening on 5.27.4 -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 434057] Add stdio mode to valgrind's gdbserver
https://bugs.kde.org/show_bug.cgi?id=434057 --- Comment #16 from Mark Wielaard --- Thanks, last patch looks pretty nice. I threw it at the try builder and it at least compiles cleanly: https://builder.sourceware.org/buildbot/#/changes/23263 That of course is all different GNU/Linux setups, maybe Paul can try it on FreeBSD. P.S. It is probably more accurate to make you the main author and add me as Co-authored-by: -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468251] After updating to 5.27.4 changing the display refresh rate on Wayland no longer works properly
https://bugs.kde.org/show_bug.cgi?id=468251 --- Comment #3 from Prajna Sariputra --- Created attachment 157930 --> https://bugs.kde.org/attachment.cgi?id=157930=edit drm_info output For what it's worth here is the output of drm_info in my case, the scaling mode reported is "None", and the listed modes there are 1920x1080@144, 1920x1080@60, and a bunch of other resolutions down to 640x480, all at 144Hz. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468251] After updating to 5.27.4 changing the display refresh rate on Wayland no longer works properly
https://bugs.kde.org/show_bug.cgi?id=468251 tju...@gmail.com changed: What|Removed |Added CC||tju...@gmail.com --- Comment #2 from tju...@gmail.com --- I have a very similar problem, since 5.27.4 KDE stays at 60fps even if I set 120,144 or 165Hz in monitor settings. Only if I set it to 170Hz will it show 170fps in the desktop effects fps meter. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 468253] New: kio_http_cache_cleaner opening connections to external IPS
https://bugs.kde.org/show_bug.cgi?id=468253 Bug ID: 468253 Summary: kio_http_cache_cleaner opening connections to external IPS Classification: Frameworks and Libraries Product: frameworks-kio Version: 5.104.0 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: HTTP Assignee: kio-bugs-n...@kde.org Reporter: foobars.dr...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- I went through the code with my limited knowledge of KDE and C++ and can't see anywhere where a https connection would be made. Examples: (Mine and someone elses) https://www.reddit.com/r/kde/comments/12eljf4/kio_http_cache_cleaner_connection_to_random_ip/ https://www.reddit.com/r/Fedora/comments/vs8m4g/kio_http_cache_cleaner_odd_behavior/ Is it related to kde feedback? STEPS TO REPRODUCE Am unable to, its not even running as a process at the moment. EXPECTED RESULT Not to make connections to external IPs SOFTWARE/OS VERSIONS kio_http_cache_cleaner version: 5.0 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468252] New: Desktop Session does not restore windows to proper screen
https://bugs.kde.org/show_bug.cgi?id=468252 Bug ID: 468252 Summary: Desktop Session does not restore windows to proper screen Classification: Plasma Product: kwin Version: 5.27.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: wickedsm...@users.sf.net Target Milestone: --- STEPS TO REPRODUCE 1. Use a two monitor (left-right) setup. The left screen is the "Primary" Device. 2. Place Konsole windows on left screen. 3. Log out, then log back in. OBSERVED RESULT The Konsole windows appear on the right screen. The window size and screen-relative placement are OK. EXPECTED RESULT The Konsole windows should appear on the left screen. SOFTWARE/OS VERSIONS Linux: Fedora 37 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION May be related to bugs marked as fixed: 427875, 442380 A work around is to set Session Restore to "When session was manually saved", place the windows on the opposite screen, then Save Session. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468115] digikam 8.0.0-Beta1 hasn't imported tags
https://bugs.kde.org/show_bug.cgi?id=468115 --- Comment #9 from caulier.gil...@gmail.com --- Forget beta1. last build is available here: https://files.kde.org/digikam/ Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 468115] digikam 8.0.0-Beta1 hasn't imported tags
https://bugs.kde.org/show_bug.cgi?id=468115 --- Comment #8 from Steve Franks --- Thank you, I’ll download beta1. Regards Steve -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468251] After updating to 5.27.4 changing the display refresh rate on Wayland no longer works properly
https://bugs.kde.org/show_bug.cgi?id=468251 --- Comment #1 from Prajna Sariputra --- Also, to be clear it's not just actively switching refresh rates that causes the problem, just setting the refresh rate to 60Hz and then rebooting means that the true refresh rate is still stuck at 144Hz when I log back into a Plasma Wayland session. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 468108] ledger freeze on large account
https://bugs.kde.org/show_bug.cgi?id=468108 Jack changed: What|Removed |Added CC|ostroffjh@users.sourceforge | |.net| --- Comment #7 from Jack --- My own data file has one account with 2815 transactions, but smaller accounts also showed similar slowness, perhaps not as extreme. How would I count the reconciliations in it? My own data file has one account with 2815 transactions, but smaller accounts also showed similar slowness, perhaps not as extreme. How would I count the reconciliations in it? Yesterday I did post a profile to the dev mailing list, and it does show one cycle, seeming to confirm the recursion. -- You are receiving this mail because: You are watching all bug changes.
