[kwin] [Bug 492152] kwin_wayland spams "kwin_scene_opengl: 0x1: GL_INVALID_VALUE in glScissor"
https://bugs.kde.org/show_bug.cgi?id=492152 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484155] Defocused fullscreen apps sometimes continue to display over everything else
https://bugs.kde.org/show_bug.cgi?id=484155 --- Comment #12 from Alex Folland --- Yes. I can reproduce it right now with the following games: - Twilight Survivors (only when set to "fullscreen" instead of "borderless fullscreen") - Yume Nikki For the record, I just tested the following games that it was happening with recently and I could no longer reproduce it in them, so I think something has improved: - Dragon Quest Heroes II - Dragon Quest XI S: Definitive Edition - Dragon Quest Monsters: The Dark Prince I believe Yume Nikki is an RPG Maker game, so I expect the issue may happen with other RPG Maker games. Yume Nikki is a free download on Steam, so that may be easy to test with. I found it by looking for free games in my library and running various ones to test the issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 484155] Defocused fullscreen apps sometimes continue to display over everything else
https://bugs.kde.org/show_bug.cgi?id=484155 Alex Folland changed: What|Removed |Added CC||lexlex...@gmail.com --- Comment #10 from Alex Folland --- I am running KWin version 6.1.5 which I believe has the committed fix from August 5th, and I still see this issue as I described today in my comment in the above-linked duplicate issue ticket. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482912] Need to use task switcher twice to switch out of a fullscreen XWayland application
https://bugs.kde.org/show_bug.cgi?id=482912 Alex Folland changed: What|Removed |Added CC||lexlex...@gmail.com --- Comment #2 from Alex Folland --- Thanks for posting this. Someone on reddit posted a workaround which didn't work for me [here](https://www.reddit.com/r/kde/comments/1bwk5lb/alt_tabbing_junkiness_in_full_screen_apps_with/), but presumably did work at some point for them. I tried unchecking "Click raises active window" then starting the game, but the alt-tab system was still super messed up when switching from the game. Here is my observed behavior with steps to reproduce: 1. Alt-tab once: The panel gets shown, but the next window doesn't get shown and stays in the background, with the game still visible. 2. If the task manager button (taskbar button) for the window I want to activate is clicked at this time, KWin just goes back to the game and hides the panel instead of showing the window I want to see, ignoring what I wanted completely. 3. If alt-tab is pressed again instead of clicking the task manager button, KWin also just goes back to the game. 4. The only way out of viewing the game without having to quit the whole game is executing the following difficult sequence correctly: 1. Alt-tab and release. - This shows the panel but not the other window, leaving the game still visible on most of the screen, and the panel on top. 2. Alt-tab and release only tab, then hold shift and press and release tab again while still holding alt and shift, then finally release all keys. - This finally results in seeing the intended window on top of the game. It's a horrible problem and makes just switching between a web browser or text editor and the game extremely uncomfortable. These are basic desktop actions. For the record, I've experienced this problem with the last 3 long games I've played through in the last month, and it's bugged me in every multi-hour play session. It's as bad as Microsoft Windows which has its own slew of alt-tab issues with fullscreen games, but at least switching works when the game is set to "borderless fullscreen", a weird Windows-only hack that the gaming industry has largely employed to work around Windows' problems with fullscreen games. I've experienced the issue recently with the following Steam games in KDE Plasma Wayland: - Dragon Quest 11 S Definitive Edition - Dragon Quest Monsters: The Dark Prince - Twilight Survivors I realize this bug tracker does not support markdown. I am using markdown still in hopes that it will some day support it. By the way, why is this marked as "minor"? It's a horrible bug that every gamer coming from Windows will experience in the first 15 minutes of gaming. The window manager is expected to be powerful enough to handle basic task switching without any issues. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 494068] New: Immediate crash on launch caused by property being unreadable
https://bugs.kde.org/show_bug.cgi?id=494068 Bug ID: 494068 Summary: Immediate crash on launch caused by property being unreadable Classification: Applications Product: kdeconnect Version: unspecified Platform: Android OS: Android 14.x Status: REPORTED Severity: crash Priority: NOR Component: android-application Assignee: albertv...@gmail.com Reporter: driverelectro6...@gmail.com CC: andrew.g.r.hol...@gmail.com Target Milestone: --- SUMMARY There's currently an issue on Android 14 that immediately crashes KDE Connect on start, presumably related to it trying to see if its input method is enabled. Since API 34, this value is not readable ( https://developer.android.com/reference/android/provider/Settings.Secure#ENABLED_INPUT_METHODS ) and InputMethodManager.getEnabledInputMethodList() ( https://developer.android.com/reference/android/view/inputmethod/InputMethodManager#getEnabledInputMethodList() ) should be used instead. KDE Connect 1.32.4 from Play Store targets API 35. STEPS TO REPRODUCE 1. Install KDE Connect from Google Play on an Android 14 device 2. Launch it 3. Connect to a device? I already have a few connections set up, maybe you need to set one up to see this. OBSERVED RESULT Immediate crash. EXPECTED RESULT App functions normally. SOFTWARE/OS VERSIONS Android 14 (crDroid 10.7, security update for Aug 5th, 2024, for miatoll) ADDITIONAL INFORMATION Log: https://paste.crdroid.net/vIuiRU p.s. the version field for kde connect bug tracker does not let me specify the proper version for the android app -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475886] Blurry window titles for some apps with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=475886 Alex B changed: What|Removed |Added CC||kde.causation251@simplelogi ||n.fr --- Comment #17 from Alex B --- I can also confirm this issue still exists (at least while running on compiled plasma on Ubuntu 24.04 [I'm aware it's not officially supported]). I have the following: Plasma 6.1.5 kded6 6.6.0 QT 6.7.2 On Wayland with AMD graphics. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493880] panel and desktop management does not save panel positions
https://bugs.kde.org/show_bug.cgi?id=493880 --- Comment #3 from Alex --- (In reply to Nate Graham from comment #2) > Aha, this! It's already fixed in 6.2.0. ok, thanks -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493787] Regression: shift+alt now opens Application Launcher
https://bugs.kde.org/show_bug.cgi?id=493787 --- Comment #2 from Gurenko Alex --- (In reply to Nate Graham from comment #1) > > *** This bug has been marked as a duplicate of bug 434988 *** I’m not sure it’s the same issue as neither shift nor alt should be a key trigger on their own, no? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493880] panel and desktop management does not save panel positions
https://bugs.kde.org/show_bug.cgi?id=493880 --- Comment #1 from Alex --- Created attachment 174236 --> https://bugs.kde.org/attachment.cgi?id=174236&action=edit panels positions before reboot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493880] New: panel and desktop management does not save panel positions
https://bugs.kde.org/show_bug.cgi?id=493880 Bug ID: 493880 Summary: panel and desktop management does not save panel positions Classification: Plasma Product: plasmashell Version: 6.1.5 Platform: Ubuntu OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: anoshkin.al...@gmail.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 174235 --> https://bugs.kde.org/attachment.cgi?id=174235&action=edit panels positions SUMMARY top panel moves constantly when restarting. i would want to create configuration as in ubuntu (top panel with left dock) STEPS TO REPRODUCE 1. add panel #1 to top side (full with) 2. add panel #2 to left side (fit content height) 3. move the top panel so that it overlaps the panel to the left (with Panel and Desktop Management) 4. reboot OBSERVED RESULT top panel does not overlaps left panel EXPECTED RESULT top panel should overlaps left panel after reboot SOFTWARE/OS VERSIONS KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Operating System: TUXEDO OS 3 (ubuntu based OS) Kernel Version: 6.11.0-102007-tuxedo (64-bit) Graphics Platform: Wayland Graphics Processor: Mesa Intel® Graphics ADDITIONAL INFORMATION screenshots: https://imgur.com/AtGQJg7 https://imgur.com/a/egxjVV3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493842] Firefox download notification goes enormous on detail
https://bugs.kde.org/show_bug.cgi?id=493842 --- Comment #1 from Gurenko Alex --- Created attachment 174210 --> https://bugs.kde.org/attachment.cgi?id=174210&action=edit Hide details after it's shown -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493842] New: Firefox download notification goes enormous on detail
https://bugs.kde.org/show_bug.cgi?id=493842 Bug ID: 493842 Summary: Firefox download notification goes enormous on detail Classification: Plasma Product: plasmashell Version: 6.1.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: agure...@protonmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 Created attachment 174209 --> https://bugs.kde.org/attachment.cgi?id=174209&action=edit Details are shown SUMMARY STEPS TO REPRODUCE 1. Try downloading https://kojipkgs.fedoraproject.org/compose/branched/Fedora-41-20240929.n.0/compose/Everything/aarch64/iso/Fedora-Everything-netinst-aarch64-41-20240929.n.0.iso in Firefox 2. Click Details OBSERVED RESULT The full link is shown as a single line enlarging the whole notification to inadeqate size. Clicking to hide details keeps notification extremely large. EXPECTED RESULT I would say the previous behavior of multi-line would be preferred and notification should go back to the normal size if details is hidden imo SOFTWARE/OS VERSIONS Operating System: Fedora Linux 41 KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.11.0-63.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C84 System Version: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493737] Some notifications are distorted and missaligned
https://bugs.kde.org/show_bug.cgi?id=493737 --- Comment #5 from Gurenko Alex --- (In reply to Nate Graham from comment #4) > I suspect this may be a different manifestation of Bug 492540, or at least > it might be fixed if we revert the changes that caused it. > > I haven't seen this particular issue myself, though. Would be good to find a > concrete way to reproduce it. I'm using Breeze Light mode, so not sure if that's it. I've tried to spam the test notifications, but those work very consistent, I think it has something to do with styling, when non-text elements are present (like Google Calendar has it's picture embedded), but that's speculation on my side -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492540] With "Vivid Dark" and other third-party Plasma themes applied, notification pop-ups blink/flicker and Plasma freezes
https://bugs.kde.org/show_bug.cgi?id=492540 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493787] New: Regression: shift+alt now opens Application Launcher
https://bugs.kde.org/show_bug.cgi?id=493787 Bug ID: 493787 Summary: Regression: shift+alt now opens Application Launcher Classification: Plasma Product: plasmashell Version: 6.1.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: plasma-b...@kde.org Reporter: agure...@protonmail.com CC: mikel5...@gmail.com, noaha...@gmail.com Target Milestone: 1.0 SUMMARY shift+alt now opens Application Launcher but is not present in shortcuts configuration STEPS TO REPRODUCE 1. Press "shift"+"alt" OBSERVED RESULT Application Launcher is opened and steals focus, minimizing fullscreen application (games for example) EXPECTED RESULT Nothing happens as it was in 6.1.5 or at least make it available somewhere (shortcut settings in Application Launcher or Global shortcuts settings) so it can be disabled SOFTWARE/OS VERSIONS Operating System: Fedora Linux 41 KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.11.0-63.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C84 System Version: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493787] Regression: shift+alt now opens Application Launcher
https://bugs.kde.org/show_bug.cgi?id=493787 Gurenko Alex changed: What|Removed |Added Keywords||regression -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493737] Some notifications are distorted and missaligned
https://bugs.kde.org/show_bug.cgi?id=493737 --- Comment #1 from Gurenko Alex --- Created attachment 174142 --> https://bugs.kde.org/attachment.cgi?id=174142&action=edit Notification after the click This is how it moves after the original is clicked -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493737] Some notifications are distorted and missaligned
https://bugs.kde.org/show_bug.cgi?id=493737 --- Comment #2 from Gurenko Alex --- Actually scratch the spacing issue, this seems to be new in 6.1.90 overall, "Notification after the click" is how the "normal" notifications are shown now -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 407667] Clicking on an expired notification in the history should launch or focus the app that sent it
https://bugs.kde.org/show_bug.cgi?id=407667 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 434954] Support firewalld zones
https://bugs.kde.org/show_bug.cgi?id=434954 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493236] Notifications blinking upon startup
https://bugs.kde.org/show_bug.cgi?id=493236 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493737] New: Some notifications are distorted and missaligned
https://bugs.kde.org/show_bug.cgi?id=493737 Bug ID: 493737 Summary: Some notifications are distorted and missaligned Classification: Plasma Product: plasmashell Version: 6.1.90 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Notifications Assignee: plasma-b...@kde.org Reporter: agure...@protonmail.com CC: k...@privat.broulik.de Target Milestone: 1.0 Created attachment 174141 --> https://bugs.kde.org/attachment.cgi?id=174141&action=edit Originally appeared notification SUMMARY Fedora 41 beta just got plasma 6.1.90 and notifications occasionally misbehave STEPS TO REPRODUCE Don't really have a steps to reproduce, but get notifications OBSERVED RESULT Some (small number of notifications) contain artifacts (white or black portions, scrambled text or moved outside of the screen). Upon clicking on it, it restores the view but moves a little to much on the left (not same alignment as "normal" notification) EXPECTED RESULT All notifications appear in a same spot and without artifacts SOFTWARE/OS VERSIONS Operating System: Fedora Linux 41 KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.11.0-63.fc41.x86_64 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C84 System Version: 1.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 480063] Bad Request after add google drive account (Plasma 6.1Dev in Neon)
https://bugs.kde.org/show_bug.cgi?id=480063 --- Comment #12 from alex <988a...@mail.ru> --- > Unfortunately I'm not able not reproduce the bug, so I'd appreciate if > someone in this report can test this patch in libkgapi. I just compile package kpim6-libkgapi-24.08.1-0zneon+22.04+jammy+release+build2 with your patch and now my google drive works without errors! Thanks for the work! -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 485865] Sharing from Krusader results in “org.kde.kdeconnect” is not installed error
https://bugs.kde.org/show_bug.cgi?id=485865 Alex Bikadorov changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||1fc5ce50f Resolution|--- |FIXED --- Comment #3 from Alex Bikadorov --- Fixed in current master (Krusader was ported to KF6.) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 488241] Export and compress entry in context menu is missing.
https://bugs.kde.org/show_bug.cgi?id=488241 Alex Bikadorov changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Version Fixed In||1fc5ce50f --- Comment #4 from Alex Bikadorov --- Fixed in current master (Krusader was ported to KF6.) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 485225] Krusader issue with mime types after P6 update
https://bugs.kde.org/show_bug.cgi?id=485225 Alex Bikadorov changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||1fc5ce50f Resolution|--- |FIXED --- Comment #6 from Alex Bikadorov --- Fixed in current master (Krusader was ported to KF6.) -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 486731] Krusader is unable to create thumbnails for pdf and other document/book formats and video formats appear as a static image instead of creating a preview for them
https://bugs.kde.org/show_bug.cgi?id=486731 Alex Bikadorov changed: What|Removed |Added Version Fixed In||1fc5ce50f Status|REOPENED|RESOLVED Resolution|--- |FIXED --- Comment #5 from Alex Bikadorov --- Fixed in current master - Krusader was ported to KF6. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 491861] If system crashes Krusader doesn't save session
https://bugs.kde.org/show_bug.cgi?id=491861 Alex Bikadorov changed: What|Removed |Added Severity|crash |wishlist CC||alex.bikado...@kdemail.net -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 480063] Bad Request after add google drive account (Plasma 6.1Dev in Neon)
https://bugs.kde.org/show_bug.cgi?id=480063 --- Comment #7 from alex <988a...@mail.ru> --- Created attachment 174015 --> https://bugs.kde.org/attachment.cgi?id=174015&action=edit dolphin kf.kio.workers.gdrive log (In reply to Elvis Angelaccio from comment #6) > If anyone can still reproduce this, please provide the output of: > > QT_LOGGING_RULES="kf.kio.workers.gdrive=true" dolphin Here is the log from last KDE Neon dev ISO - neon-developer-20240729-1603.iso -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 493443] New: Spectacle problem dual monitor
https://bugs.kde.org/show_bug.cgi?id=493443 Bug ID: 493443 Summary: Spectacle problem dual monitor Classification: Applications Product: Spectacle Version: 23.08.5 Platform: Kubuntu OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: General Assignee: noaha...@gmail.com Reporter: huo...@mailto.plus CC: k...@david-redondo.de Target Milestone: --- Created attachment 173938 --> https://bugs.kde.org/attachment.cgi?id=173938&action=edit photo of bug When using two monitors and trying to take a screenshot, this problem occurs, the screen area is simply torn, while the graphics are in their places, if you try to select the area that has shifted to capture the image, a completely different area is selected. When using one monitor, there is no such problem. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 483148] TM context menu "Move to [activity name]" doesn't move window, and instead shows window on all activities
https://bugs.kde.org/show_bug.cgi?id=483148 alex <988a...@mail.ru> changed: What|Removed |Added CC||988a...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kio-gdrive] [Bug 480063] Bad Request after add google drive account (Plasma 6.1Dev in Neon)
https://bugs.kde.org/show_bug.cgi?id=480063 alex <988a...@mail.ru> changed: What|Removed |Added CC||988a...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[marble] [Bug 493372] New: Crash with vector OSM - Marble::VisiblePlacemark::symbolRect
https://bugs.kde.org/show_bug.cgi?id=493372 Bug ID: 493372 Summary: Crash with vector OSM - Marble::VisiblePlacemark::symbolRect Classification: Applications Product: marble Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: marble-b...@kde.org Reporter: alex.danila@protonmail.com Target Milestone: --- Browsing with Vector OSM will many times lead to crashes. It seems like browsing faster (frequent mouse actions with triggering map downloads). Crash stack: Application: Globe Virtuel Marble (marble), signal: Segmentation fault [KCrash Handler] #4 0x7f49eb5d001f in QPixmap::size() const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #5 0x7f49ecd51fec in Marble::VisiblePlacemark::symbolRect (this=this@entry=0x55621ef15a30) at ./src/lib/marble/VisiblePlacemark.cpp:167 #6 0x7f49ecd5417b in Marble::PlacemarkLayout::hasPlacemarkAt (this=0x55620dcb1ae8, pos=...) at ./src/lib/marble/PlacemarkLayout.cpp:550 #7 0x7f49ecc6942d in Marble::PlacemarkLayer::hasPlacemarkAt (this=, pos=...) at ./src/lib/marble/layers/PlacemarkLayer.cpp:212 #8 0x7f49ecc9f07e in Marble::MarbleMap::hasFeatureAt (this=0x55620dcdaa90, position=...) at ./src/lib/marble/MarbleMap.cpp:477 #9 0x7f49ecce8232 in Marble::MarbleDefaultInputHandler::adjustCursorShape (this=this@entry=0x55620df1b6d0, mousePosition=..., mouseDirection=...) at ./src/lib/marble/MarbleInputHandler.cpp:670 #10 0x7f49ecce971a in Marble::MarbleDefaultInputHandler::handleMouseEvent (this=0x55620df1b6d0, event=0x7fff03aabcb0) at ./src/lib/marble/MarbleInputHandler.cpp:894 #11 0x7f49eb0de0f3 in QCoreApplicationPrivate::sendThroughObjectEventFilters (receiver=receiver@entry=0x55620dcd5110, event=event@entry=0x7fff03aabcb0) at kernel/qcoreapplication.cpp:1190 #12 0x7f49ebd63082 in QApplicationPrivate::notify_helper (this=this@entry=0x55620d727ea0, receiver=receiver@entry=0x55620dcd5110, e=e@entry=0x7fff03aabcb0) at kernel/qapplication.cpp:3634 #13 0x7f49ebd6b3ba in QApplication::notify (this=, receiver=0x55620dcd5110, e=0x7fff03aabcb0) at kernel/qapplication.cpp:3084 #14 0x7f49eb0de398 in QCoreApplication::notifyInternal2 (receiver=0x55620dcd5110, event=0x7fff03aabcb0) at kernel/qcoreapplication.cpp:1064 #15 0x7f49eb0de5a2 in QCoreApplication::sendSpontaneousEvent (receiver=, event=) at kernel/qcoreapplication.cpp:1474 #16 0x7f49ebd69442 in QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x55620dcd5110, event=event@entry=0x7fff03aabcb0, alienWidget=, nativeWidget=0x55620dcdece0, buttonDown=buttonDown@entry=0x7f49ec2c39d0 , lastMouseReceiver=..., spontaneous=true, onlyDispatchEnterLeave=false) at kernel/qapplication.cpp:2622 #17 0x7f49ebdbfd7a in QWidgetWindow::handleMouseEvent (this=this@entry=0x55620eb9e1f0, event=event@entry=0x7fff03aabf80) at kernel/qwidgetwindow.cpp:684 #18 0x7f49ebdc328f in QWidgetWindow::event (this=0x55620eb9e1f0, event=0x7fff03aabf80) at kernel/qwidgetwindow.cpp:300 #19 0x7f49ebd63092 in QApplicationPrivate::notify_helper (this=, receiver=0x55620eb9e1f0, e=0x7fff03aabf80) at kernel/qapplication.cpp:3640 #20 0x7f49eb0de398 in QCoreApplication::notifyInternal2 (receiver=0x55620eb9e1f0, event=0x7fff03aabf80) at kernel/qcoreapplication.cpp:1064 #21 0x7f49eb544c63 in QGuiApplicationPrivate::processMouseEvent(QWindowSystemInterfacePrivate::MouseEvent*) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #22 0x7f49eb5166fc in QWindowSystemInterface::sendWindowSystemEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #23 0x7f49ce2c596e in ?? () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #24 0x7f49e970c7df in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #25 0x7f49e970ea17 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #26 0x7f49e970f180 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #27 0x7f49eb13b1ed in QEventDispatcherGlib::processEvents (this=0x55620d860750, flags=...) at kernel/qeventdispatcher_glib.cpp:423 #28 0x7f49eb0dcd02 in QEventLoop::exec (this=this@entry=0x7fff03aac320, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69 #29 0x7f49eb0e5722 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121 #30 0x5561fd12409a in main (argc=, argv=) at ./src/apps/marble-kde/kdemain.cpp:441 [Inferior 1 (process 15680) detached] STEPS TO REPRODUCE 1. Switch Marble vector OSM. 2. Start browsing fast, triggering new map region downloads. OBSERVED RESULT Crash. EXPECTED RESULT SOFTWARE/OS VERSIONS Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Kernel Version: 6.10.9-amd64 (64-bit) Graphics Platform: offscreen Processor
[Spectacle] [Bug 480888] Area capture selector goes under the floating panel
https://bugs.kde.org/show_bug.cgi?id=480888 --- Comment #29 from Gurenko Alex --- Tested on following software configuration: Operating System: Fedora Linux 41 KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.2 Kernel Version: 6.11.0-63.fc41.x86_64 (64-bit) Graphics Platform: Wayland Worked as expected with amdgpu (RX 7900XTX), i915 (Intel UHD620 on Lenovo P1 gen2), Pinebook Pro. Works with both floating and non-floating bar right now. I guess we can close it as it was fixed at some point recently. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 480888] Area capture selector goes under the floating panel
https://bugs.kde.org/show_bug.cgi?id=480888 --- Comment #28 from Gurenko Alex --- I still saw the issue few weeks ago, it got more consistent (as in it generally works), right now does not reproduce with latest versions of everything, let me go over my devices (amdgpu, intel gpu, arm mali gpu) and see where we stand with the latest stack. I just got all my devices to Fedora 41 beta with fresh mesa. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469440] The Media Control Applet crashes Plasma at QOpenGLContext::functions()
https://bugs.kde.org/show_bug.cgi?id=469440 --- Comment #28 from Alex --- Would you want/need a new stacktrace if I can reproduce with Plasma 6? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469440] The Media Control Applet crashes Plasma at QOpenGLContext::functions()
https://bugs.kde.org/show_bug.cgi?id=469440 Alex changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #26 from Alex --- Still waiting on Debian, which Ships 5.27.11-1 in Trixie and Sid. I'd also happy to finally get Plasma 6, but they seem to need their time, bot. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493176] Incorrect widget rendering in vertical panel
https://bugs.kde.org/show_bug.cgi?id=493176 --- Comment #1 from Alex --- Created attachment 173707 --> https://bugs.kde.org/attachment.cgi?id=173707&action=edit Same widgets as the KDE 5 widgets but with KDE 6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 493176] New: Incorrect widget rendering in vertical panel
https://bugs.kde.org/show_bug.cgi?id=493176 Bug ID: 493176 Summary: Incorrect widget rendering in vertical panel Classification: Plasma Product: plasmashell Version: 6.1.4 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: alo...@gmail.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 173706 --> https://bugs.kde.org/attachment.cgi?id=173706&action=edit Working vertical widgets with KDE 5 back in January SUMMARY KDE 6 Seems to have broken system monitor widget rendering for vertical panels. STEPS TO REPRODUCE 1. Create a vertical panel (application menu bar, empty panel, floating or not, same result) 2. Set the width to a sane number such as 200 pixel width 3. Add a system monitor widget such as disk activity, network, etc 4. Specify a title and check "Show Title" OBSERVED RESULT 1. The title does not appear (for at least text/line/grid/bar chart widgets) 2. For text only display styles, the labels wrap in 2 columns 3. Line charts do not show the legend or grid lines 4. Widgets seem to be compressed vertically EXPECTED RESULT 1. Titles properly show 2. Text only widgets show a single label per row 3. Charts show legend labels and lines SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.9-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 32 × AMD Ryzen 9 7950X3D 16-Core Processor Memory: 61.9 GiB of RAM Graphics Processor: AMD Radeon RX 6900 XT ADDITIONAL INFORMATION The use case is a still visible panel of perf widgets even when maximizing a window on the screen, used on a second monitor. This worked in KDE 5, see attached images -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472340] OLED subpixel rendering support
https://bugs.kde.org/show_bug.cgi?id=472340 Alex Folland changed: What|Removed |Added CC||lexlex...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kidletime] [Bug 328987] Power saving should not trigger if joystick/controller/gamepad is in use
https://bugs.kde.org/show_bug.cgi?id=328987 Alex Folland changed: What|Removed |Added CC||lexlex...@gmail.com --- Comment #61 from Alex Folland --- I was not having this issue on KDE Plasma 6 until about the middle of last week. Somehow it started last week, and now I have to use a workaround of setting "Sleep and Screen Locking after Inactivity" to "Blocked" in the Plasma "Power Management" menu that's accessed from the panel's "System Tray" widget's "Power Management" icon. It didn't happen before last week, even though I have been playing the same game as I was before last week regularly. I am using Manjaro with the "unstable" set of repositories, which gets updates consistently multiple times per day from the Arch Linux "stable" set of repositories, and I regularly update my system daily, with a full reboot each time. Therefore, I expect that some update I applied last week caused this to happen. I'm not sure what the exact update was, but here's the current output of `pacman -Qi kidletime` which shows the version of the `kidletime` package I have installed right now: [alex@alex-pc ~]$ pacman -Qi kidletime Name: kidletime Version : 6.5.0-1 Description : Monitoring user activity Architecture: x86_64 URL : https://community.kde.org/Frameworks Licenses: LGPL-2.0-only LGPL-3.0-only Groups : kf6 Provides: None Depends On : gcc-libs glibc qt6-base Optional Deps : libx11: XCB plugin [installed] libxcb: XCB plugin [installed] libxext: XCB plugin [installed] libxss: XCB plugin [installed] qt6-wayland: Wayland plugin [installed] wayland: Wayland plugin [installed] Required By : baloo discover drkonqi konversation kscreenlocker kwin plasma-workspace powerdevil Optional For: None Conflicts With : None Replaces: None Installed Size : 395.11 KiB Packager: Tomaz Canabrava Build Date : Fri 09 Aug 2024 07:32:20 PDT Install Date: Thu 05 Sep 2024 12:09:31 PDT Install Reason : Installed as a dependency for another package Install Script : No Validated By: Signature [alex@alex-pc ~]$ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 492027] Monitor does not turn on after automatic turn off
https://bugs.kde.org/show_bug.cgi?id=492027 --- Comment #7 from Gurenko Alex --- For tracking purposes, I've opened issue upstream: https://gitlab.freedesktop.org/drm/amd/-/issues/3608 -- You are receiving this mail because: You are watching all bug changes.
[ark] [Bug 441608] Ark fails to unzip file with message about compression method not supported
https://bugs.kde.org/show_bug.cgi?id=441608 Alex Folland changed: What|Removed |Added CC||lexlex...@gmail.com --- Comment #8 from Alex Folland --- I encountered this today when extracting a very popular game mod. Of course, the workaround of disabling "libzip" worked, but anyone with a default KDE installation who tries to extract that mod will encounter this, which is a huge problem for the desktop's popularity. It makes the Linux ecosystem look much worse than it should, since even the Windows built-in compression tool can handle that game mod. I suggest that this be made a high-priority issue to prevent common gamers from feeling like the Linux ecosystem is not ready for daily use. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 492027] Monitor does not turn on after automatic turn off
https://bugs.kde.org/show_bug.cgi?id=492027 --- Comment #6 from Gurenko Alex --- (In reply to Zamundaaa from comment #5) > Hmm, then it's not our bug I'm afraid - if the display was still off from > KWin's perspective, the drm_info output would say so. > You might have better luck at > https://gitlab.freedesktop.org/drm/amd/-/issues, but it sounds like it's a > monitor issue and not caused by the video source. Maybe it goes into some > deeper power state where you need to press a button on the monitor, or maybe > something's more broken with it. It was working perfectly fine between 6.0 beta 1 and 6.1 (not inclusive). I'll try opening issue for amdgpu, just in case, but I don't see why is it set to resolved now -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470630] Incorrect opening of a folder when a terminal window is running
https://bugs.kde.org/show_bug.cgi?id=470630 Alex <7...@mail.ru> changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #4 from Alex <7...@mail.ru> --- The problem disappeared after some update -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 492027] Monitor does not turn on after automatic turn off
https://bugs.kde.org/show_bug.cgi?id=492027 --- Comment #4 from Gurenko Alex --- (In reply to Zamundaaa from comment #3) > 6.2 is not out yet, and neither is 6.1.5. > > After waking up, is there anything suspicious in KWin's log? You can get it > with > > journalctl --user-unit plasma-kwin_wayland --boot 0 > > Also, what's the output of drm_info when the screen doesn't turn on? So, I've connected to the machine over ssh to monitor what's happening there and...not much... I've captured two drm_info outputs, one before locking and one after the screen didn't wake up the only difference is one of the IDs changed: ``` $ diff ./drm-normal drm-failed 882,883c882,883 < │ │ ├───FB ID: 132 < │ │ │ ├───Object ID: 132 --- > │ │ ├───FB ID: 131 > │ │ │ ├───Object ID: 131 914,915c914,915 < │ ├───"FB_ID" (atomic): object framebuffer = 132 < │ │ ├───Object ID: 132 --- > │ ├───"FB_ID" (atomic): object framebuffer = 131 > │ │ ├───Object ID: 131 ``` the output of the journal: ``` Sep 02 20:04:34 wasp-blackquiet kscreenlocker_greet[23841]: Failed to write to the pipe: Bad file descriptor. Sep 02 20:42:04 wasp-blackquiet kwin_wayland[2208]: kwin_screencast: PipeWire remote error: connection error Sep 02 20:42:05 wasp-blackquiet systemd[1892]: Stopping plasma-kwin_wayland.service - KDE Window Manager... Sep 02 20:42:05 wasp-blackquiet kscreenlocker_greet[24155]: pam_unix(kde:auth): authentication failure; logname=agurenko uid=1000 euid=1000 tty= ruser= rh> Sep 02 20:42:05 wasp-blackquiet kscreenlocker_greet[24155]: Failed to write to the pipe: Bad file descriptor. Sep 02 20:42:05 wasp-blackquiet systemd[1892]: Stopped plasma-kwin_wayland.service - KDE Window Manager. Sep 02 20:42:05 wasp-blackquiet systemd[1892]: plasma-kwin_wayland.service: Consumed 9min 41.236s CPU time. ``` The last record, looks like when I moved the mouse is: > Sep 02 20:41:21 org_kde_powerdevil[2550]: dh=Display_Handle[i2c-6: fd=31], > Keeping adjusted sleep multiplier 1.30 for SE_POST_WRITE or > SE_POST_SAVE_SETTINGS Otherwise, literally no records in the syslog -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 492503] Opening files >8192x8192 (>67108864 pixels overall) fails after latest update
https://bugs.kde.org/show_bug.cgi?id=492503 --- Comment #4 from Alex --- edit to my last comment: $ export QT_IMAGEIO_MAXALLOC=0 works also, I expect functionally the same as code doing QImageReader::setAllocationLimit(0) -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 492503] Opening files >8192x8192 (>67108864 pixels overall) fails after latest update
https://bugs.kde.org/show_bug.cgi?id=492503 --- Comment #3 from Alex --- So, seems like a workaround for this is to set the QT_IMAGEIO_MAXALLOC environment variable according to https://doc.qt.io/qt-6/qimagereader.html. Doing: $ export QT_IMAGEIO_MAXALLOC=8192 $ kolourpaint allows me to open large files again (8192MiB may be overkill for my needs currently, but you get the point you can define an arbitrary value). Seems like the fix would be for kolourpaint to set QImageReader::setAllocationLimit(0). Amusingly, the preview that shows up in the File -> Open dialog works regardless of what limit is set, so maybe the above is already done for that. -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 492503] Opening files >8192x8192 (>67108864 pixels overall) fails after latest update
https://bugs.kde.org/show_bug.cgi?id=492503 Alex changed: What|Removed |Added CC||kdeb...@cubelike.com -- You are receiving this mail because: You are watching all bug changes.
[kolourpaint] [Bug 492503] New: Opening files >8192x8192 (>67108864 pixels overall) fails after latest update
https://bugs.kde.org/show_bug.cgi?id=492503
Bug ID: 492503
Summary: Opening files >8192x8192 (>67108864 pixels overall)
fails after latest update
Classification: Applications
Product: kolourpaint
Version: 24.08.0
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: major
Priority: NOR
Component: general
Assignee: kolourpaint-supp...@lists.sourceforge.net
Reporter: kdeb...@cubelike.com
Target Milestone: ---
Created attachment 173203
--> https://bugs.kde.org/attachment.cgi?id=173203&action=edit
Error shown when loading large file.
SUMMARY
Opening files >8192x8192 (>67108864 pixels overall) fails after latest update.
STEPS TO REPRODUCE
1. Open kolourpaint and goto "Image -> Resize/Scale".
2. Click "Resize" and set height and width to 8193
3. Save and close the file
4. Try to open the file, you will see the error: 'Could not open
"{$filename}" - unsupported image format.'
The file may be corrupt.
OBSERVED RESULT
Kolourpaint fails to load the file and renders a blank (white) cavas 2048x2048
pixels on starting.
EXPECTED RESULT
Kolourpaint loads and displays the file.
SOFTWARE/OS VERSIONS
OS: Fedora release 40 (Forty)
KDE Frameworks Version: 6.5.0
Qt Version: 6.7.2 (built against 6.7.2)
ADDITIONAL INFORMATION
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 469440] The Media Control Applet crashes Plasma at QOpenGLContext::functions()
https://bugs.kde.org/show_bug.cgi?id=469440 --- Comment #23 from Alex --- In addition I see a few recent duplicates, which probably mean that the bug may indeed still be in more recent plasma versions. That's why I WILL test it in my setup, once Debian manages to get recent packages. I wonder what's the blocker on their side, but that's another story. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469440] The Media Control Applet crashes Plasma at QOpenGLContext::functions()
https://bugs.kde.org/show_bug.cgi?id=469440 --- Comment #22 from Alex --- (In reply to Justin Zobel from comment #21) > Hi Alex, I see you changed the bug back to reported, but no additional > information was provided. Were you able to test Plasma 6 and confirm if this > crash still occurs? I changed it back, because the stupid bot will otherwise close the bug before I get a chance to test it, and I am still waiting on Debian packages. It seems that removing the NEEDSINFO tag is the only way to stop the bot from automatically closing the bug before I get the chance to give feedback, so I had to remove it. Tell me, if there are other ways to disable the bot, as the NEEDSINFO flag is, without the bot, a nice reminder that I still intend to give feedback. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 492027] Monitor does not turn on after automatic turn off
https://bugs.kde.org/show_bug.cgi?id=492027 --- Comment #2 from Gurenko Alex --- So, it looks like it missed 6.2 release already, but can we still get the ball rolling here? I'm happy to provide additional information if you tell me what it is you need -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 492149] New: Make OpenVPN's `inactive` setting usable in the UI
https://bugs.kde.org/show_bug.cgi?id=492149 Bug ID: 492149 Summary: Make OpenVPN's `inactive` setting usable in the UI Classification: Plasma Product: plasma-nm Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: editor Assignee: plasma-b...@kde.org Reporter: a...@cluonflux.com Target Milestone: --- SUMMARY OpenVPN has an `inactive` setting that can be used to automatically shut down the VPN based on idle time and/or a lack of traffic. It'd be great if this could be made available in the plasma-nm-openvpn UI. :) STEPS TO REPRODUCE 1. Create OpenVPN connection, perhaps by importing a .ovpn profile from a file 2. Go to the Advanced dialog of the connection configuration page OBSERVED RESULT There's no widget for the `inactive` setting EXPECTED RESULT It'd be nice to have widgets for the `inactive` setting ;) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora 40, plasma-nm-openvpn 6.1.4-1.fc40, openvpn 2.6.12-1.fc40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Here's the relevant section from the OpenVPN docs... sadly there are no anchors on the page: --inactive args Causes OpenVPN to exit after n seconds of inactivity on the TUN/TAP device. The time length of inactivity is measured since the last incoming or outgoing tunnel packet. The default value is 0 seconds, which disables this feature. Valid syntaxes: inactive n inactive n bytes If the optional bytes parameter is included, exit if less than bytes of combined in/out traffic are produced on the tun/tap device in n seconds. In any case, OpenVPN's internal ping packets (which are just keepalives) and TLS control packets are not considered "activity", nor are they counted as traffic, as they are used internally by OpenVPN and are not an indication of actual user activity. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 491865] plasmashell crashes in pw_stream_dequeue_buffer() after PipeWireSourceStream::process()
https://bugs.kde.org/show_bug.cgi?id=491865 Alex Ball changed: What|Removed |Added CC||a.j.b...@bath.ac.uk -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 492022] Plasmashell crashing
https://bugs.kde.org/show_bug.cgi?id=492022 Alex Ball changed: What|Removed |Added CC||a.j.b...@bath.ac.uk -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488704] [KDE Plasma 6.1.0] Monitor unable to turn on after idle.
https://bugs.kde.org/show_bug.cgi?id=488704 --- Comment #6 from Gurenko Alex --- (In reply to Nate Graham from comment #5) > Aha, that means your issue is subtly different, Alex. Can you open a new bug > report about it? Sure, I've opened https://bugs.kde.org/show_bug.cgi?id=492027 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 492027] New: Monitor does not turn on after automatic turn off
https://bugs.kde.org/show_bug.cgi?id=492027 Bug ID: 492027 Summary: Monitor does not turn on after automatic turn off Classification: Plasma Product: kwin Version: 6.1.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: multi-screen Assignee: kwin-bugs-n...@kde.org Reporter: agure...@protonmail.com Target Milestone: --- Created attachment 172846 --> https://bugs.kde.org/attachment.cgi?id=172846&action=edit Screen Settings SUMMARY I've been having a problem with "Turn off screen" feature after around Plasma 6.1 update. It was definitely working for me during the Plasma 6 beta time frame, I think it also works for 6.0.x. Now at 6.1.4 I still have a problem. STEPS TO REPRODUCE 1. Enable Turn off screen and set it to 30 minutes and When locked: 1 minute 2. Lock the screen 3. Wait until the screen goes off and wait few more minutes 4. Move the mouse and/or press any button OBSERVED RESULT Screen does not turn on. Even more, if I force shutdown the PC and turn it on, screen still does not turn on, it requires a power cycle by unplugging it from the wall. EXPECTED RESULT Screen will turn on SOFTWARE/OS VERSIONS: Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.6-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C84 System Version: 1.0 ADDITIONAL INFORMATION In most cases, if I try to wake the screen *right after* it goes off, it turns back on right away, but after a few minutes it's 100% reproducible. I have Dell S2721dgfa monitor connected over DisplayPort cable, set to 165 Hz, it's a FreeSync Enabled screen with HDR support, I do have HDR set to off, I do have custom ICM profile applied, I do have 125% scaling enabled. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488704] [KDE Plasma 6.1.0] Monitor unable to turn on after idle.
https://bugs.kde.org/show_bug.cgi?id=488704 --- Comment #3 from Gurenko Alex --- Forgot to add, that actually I cannot get the monitor to display anything after the said issue occurs, until I power cycle it with cable removal -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488704] [KDE Plasma 6.1.0] Monitor unable to turn on after idle.
https://bugs.kde.org/show_bug.cgi?id=488704 --- Comment #2 from Gurenko Alex --- Just to add visibility to this issue, I'm experiencing it for a long time as well, it was definitely working during the beta time frame of Plasma 6 and I guess it broke around 6.1 release. Operating System: Fedora Linux 40 KDE Plasma Version: 6.1.4 KDE Frameworks Version: 6.5.0 Qt Version: 6.7.2 Kernel Version: 6.10.6-200.fc40.x86_64 (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 5900X 12-Core Processor Memory: 31.3 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C84 System Version: 1.0 My monitor is Dell S2721dgfa connected over DisplayPort -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 488704] [KDE Plasma 6.1.0] Monitor unable to turn on after idle.
https://bugs.kde.org/show_bug.cgi?id=488704 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 491863] The root password
https://bugs.kde.org/show_bug.cgi?id=491863 Alex Geer changed: What|Removed |Added Status|REOPENED|RESOLVED Resolution|--- |NOT A BUG --- Comment #11 from Alex Geer --- You're wrong. Believe me, I'm not going to offend anyone, but if honest words are an insult to you, there's nothing I can do to help you. You probably got to the bottom of the reason for the appeal, along with your unwillingness to solve the problem, this led you to the false conclusion that you were being insulted. It is ok. You are who you are and no one will change that. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 491863] The root password
https://bugs.kde.org/show_bug.cgi?id=491863 Alex Geer changed: What|Removed |Added Resolution|--- |NOT A BUG Status|REOPENED|RESOLVED --- Comment #9 from Alex Geer --- I think it's worth closing this discussion. I understood everything perfectly. I deleted the app Discover. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 491863] The root password
https://bugs.kde.org/show_bug.cgi?id=491863 --- Comment #8 from Alex Geer --- (In reply to Nicolas Fella from comment #7) > Alex, your conduct here is unacceptable. Calling things "crime against > humanity" and blindly assuming incompetence are not constructive ways to > talk about an issue. > > Please familiarize yourself with the KDE Code of Conduct > (https://kde.org/code-of-conduct/) before further engaging with KDE I'm sorry, I forgot a little that I'm dealing with a world that accepts what happens at the Olympics, all perversions and crimes are acceptable, but honesty and truth are not acceptable. I was wrong. You're great! keep it up ! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 491863] The root password
https://bugs.kde.org/show_bug.cgi?id=491863 --- Comment #6 from Alex Geer --- (In reply to fanzhuyifan from comment #4) > (In reply to Alex Geer from comment #2) > > Shifting the problem to another area of responsibility does not improve your > > application, but only speaks of incompetence. > > > > There is nothing stopping you from adding password memorization to the > > application during the session instead of shifting the problem to openSUSE. > > Unfortunately storing the root password in memory is not something that we > can feasibly do without imposing security risks. Can you check if the user has sudo and use it? -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 491863] The root password
https://bugs.kde.org/show_bug.cgi?id=491863 Alex Geer changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|DOWNSTREAM |--- --- Comment #5 from Alex Geer --- Not at all. You're just showing your unwillingness to do anything at all. I work under a user who is allowed sudo, you could check this from the application and not ask for the root password at all. I mentioned competence for a reason. You should not refer to the fact that this is not your problem or take responsibility for security when you are not asked to do so. If the user checks the "Save password" box, then the user assumes responsibility of security risk. Please do not confuse safety with laziness. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 491863] The root password
https://bugs.kde.org/show_bug.cgi?id=491863 Alex Geer changed: What|Removed |Added Resolution|DOWNSTREAM |--- Ever confirmed|0 |1 Status|RESOLVED|REOPENED --- Comment #3 from Alex Geer --- But of course it's up to you. I have to delete this misunderstanding called the application. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 491863] The root password
https://bugs.kde.org/show_bug.cgi?id=491863 --- Comment #2 from Alex Geer --- Shifting the problem to another area of responsibility does not improve your application, but only speaks of incompetence. There is nothing stopping you from adding password memorization to the application during the session instead of shifting the problem to openSUSE. Refine the application to a professional level and it will work on any Linux, instead of unsubscribing that this is not your problem and read there and there. At least that's what the professionals would do. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 491863] The root password
https://bugs.kde.org/show_bug.cgi?id=491863 Alex Geer changed: What|Removed |Added Platform|Other |openSUSE -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 491863] New: The root password
https://bugs.kde.org/show_bug.cgi?id=491863 Bug ID: 491863 Summary: The root password Classification: Applications Product: Discover Version: 5.27.11 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: plasma-b...@kde.org Reporter: bo...@mail.ru CC: aleix...@kde.org Target Milestone: --- Now, when installing updates through the Discovery program, I had to enter the root password 78 times in a row. Not to call it bullying would be a crime against humanity. What prevents you from checking the "Remember password" box and storing it in memory while the program is running? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 491677] Blurred icons when using fractional scaling (Qt 6.8, frameworks and plasma master)
https://bugs.kde.org/show_bug.cgi?id=491677 --- Comment #4 from Alex Fiestas --- Awesome, I can confirm that the patch fixes the issue for me. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 491677] Blurred icons when using fractional scaling (Qt 6.8, frameworks and plasma master)
https://bugs.kde.org/show_bug.cgi?id=491677 --- Comment #1 from Alex Fiestas --- Created attachment 172590 --> https://bugs.kde.org/attachment.cgi?id=172590&action=edit Video where the blurry icons can be observed. Scaled down to 1080 from 4k but the icon blurriness can be observed. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kiconthemes] [Bug 491677] New: Blurred icons when using fractional scaling (Qt 6.8, frameworks and plasma master)
https://bugs.kde.org/show_bug.cgi?id=491677 Bug ID: 491677 Summary: Blurred icons when using fractional scaling (Qt 6.8, frameworks and plasma master) Classification: Frameworks and Libraries Product: frameworks-kiconthemes Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: cf...@kde.org Reporter: afies...@kde.org CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY While using latest Qt 6.8 + frameworks + plasma from master icons in Qt apps and some icons in plasma are blurred as long as I have fractional scaling enabled. STEPS TO REPRODUCE 1. Enable fractional scaling 2. open kwrite or 2. open a plasma popup OBSERVED RESULT Icons are blurry EXPECTED RESULT Icons should be sharp. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch, updated regularly. KDE Plasma Version: Master, compiled KDE Frameworks Version: Master, compiled Qt Version: 6.8 from qt5.git branch ADDITIONAL INFORMATION I can patch and recompile if more information is needed. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 481922] The Quick Launch icons on the taskbar cannot be freely rearranged
https://bugs.kde.org/show_bug.cgi?id=481922 Alex Folland changed: What|Removed |Added CC||lexlex...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 430333] Wrong position for list command for each tab in Krusader GUI
https://bugs.kde.org/show_bug.cgi?id=430333 Alex Bikadorov changed: What|Removed |Added Status|REPORTED|NEEDSINFO CC||alex.bikado...@kdemail.net Resolution|--- |WAITINGFORINFO --- Comment #15 from Alex Bikadorov --- I believe this issue of popup menus being displayed at a wrong position has been fixed some time ago (in Qt). If there are no contrary observations, this ticket can be closed. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 438814] Default fonts of titler cause "Clip Problems" when opening project
https://bugs.kde.org/show_bug.cgi?id=438814 Alex changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |FIXED --- Comment #2 from Alex --- Issue seems to be fixed now. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489892] Triangle filter for multi-window thumbnail popup is not working properly, causing popup to close or switch to thumbnails of another app too eagerly
https://bugs.kde.org/show_bug.cgi?id=489892 --- Comment #19 from Alex --- I think my problem is not covered by the current filter even when working correctly, if I understand the filter the right way. Currently it avoids, if I understand it correctly, that moving from an application icon to a preview switches to previews of another application when the mouse crosses the other applications's icon, e.g, a triangle with the apex at the launcher icon. Once the mouse moves over the previews, there should probably be a new (or second) triangle with the apex at the preview and not at the launcher icon protecting the path along the axis of the previews. I am not even sure if it should be a triangle, because it would probably need to be something that moves along with the cursor (why should the first preview stay the reference point?) and then I wonder if a triangle would even be the correct shape for that. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 491359] New: matrix.to links not opening rooms
https://bugs.kde.org/show_bug.cgi?id=491359 Bug ID: 491359 Summary: matrix.to links not opening rooms Classification: Applications Product: NeoChat Version: 24.05.2 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: len...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY Element users send matrix.to links, but Neochat isn't opening those rooms. STEPS TO REPRODUCE 1. Receive a message with this link on an account that federates with ubuntu.com: https://matrix.to/#/#rockcraft:ubuntu.com 2. Click the link Expected: Neochat joins the room and switches to it, previews the room, or otherwise provides some user response Actual: Neochat seems to do nothing. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 398248] copy progress is not shown in Gnome
https://bugs.kde.org/show_bug.cgi?id=398248 Alex Bikadorov changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #3 from Alex Bikadorov --- Still an issue or can this bug be closed? -- You are receiving this mail because: You are watching all bug changes.
[konqueror] [Bug 491256] New: Browser displays graphical glitches instead of webpage (HW acceleration issue?)
https://bugs.kde.org/show_bug.cgi?id=491256 Bug ID: 491256 Summary: Browser displays graphical glitches instead of webpage (HW acceleration issue?) Classification: Applications Product: konqueror Version: 22.12.3 Platform: Debian stable OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: webenginepart Assignee: konq-b...@kde.org Reporter: cahbka...@mail.ru Target Milestone: --- Created attachment 172268 --> https://bugs.kde.org/attachment.cgi?id=172268&action=edit Screenshot of Konquerior window when bug is reproduced SUMMARY I have graphical glitches only in konquerior but no other programs (i can use other browsers, play 3D games, work in KiCad, etc. without any graphical bugs). Bug can be correctly screenshoted. STEPS TO REPRODUCE 1. Get AMD RX6800XT 2. Install amdgpu driver (amdgpu-core 1:6.1.60101-1769056.22.04) 3. Reboot and open any webpage OBSERVED RESULT Graphical garbage in webpage rendering zone EXPECTED RESULT Web page ;) SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian Bookworm KDE Plasma Version: plasma-workspace/stable-security,now 4:5.27.5-2+deb12u2 KDE Frameworks Version: What is KDE frameworks? (apt list *kde*framework* - no such packages) Qt Version: 6.4.2+dfsg-10 -- You are receiving this mail because: You are watching all bug changes.
[knights] [Bug 491204] New game set up
https://bugs.kde.org/show_bug.cgi?id=491204 alex.hu...@gmail.com changed: What|Removed |Added Platform|Other |openSUSE Version|unspecified |2.6.24052 -- You are receiving this mail because: You are watching all bug changes.
[knights] [Bug 491204] New: New game set up
https://bugs.kde.org/show_bug.cgi?id=491204 Bug ID: 491204 Summary: New game set up Classification: Applications Product: knights Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.se...@web.de Reporter: alex.hu...@gmail.com CC: kde-games-b...@kde.org Target Milestone: --- *** If you're not sure this is actually a bug, instead post about it at https://discuss.kde.org If you're reporting a crash, attach a backtrace with debug symbols; see https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** SUMMARY STEPS TO REPRODUCE 1. start app 2. try to play 3. OBSERVED RESULT can't play EXPECTED RESULT can play SOFTWARE/OS VERSIONS Windows: macOS: (available in the Info Center app, or by running `kinfo` in a terminal window) Linux/KDE Plasma: open SuSE Tumbleweed slowroll KDE Plasma Version: 6.1.3 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.2 ADDITIONAL INFORMATION Hi, when you start Knights, the chessboard will be created straight away, but it can't be used. You've to click on "new" to set up a new game before you can use the app. Can the dialog for setting up the game be shown directly after the app start? kind regards alex -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 490421] PowerDevil crash in Core::onKIdleTimeoutReached()
https://bugs.kde.org/show_bug.cgi?id=490421 Gurenko Alex changed: What|Removed |Added CC||agure...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 485865] Sharing from Krusader results in “org.kde.kdeconnect” is not installed error
https://bugs.kde.org/show_bug.cgi?id=485865 Alex Bikadorov changed: What|Removed |Added CC||m...@stantoncentral.co.uk --- Comment #2 from Alex Bikadorov --- *** Bug 490840 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 490840] Share with "Send to Device" fails
https://bugs.kde.org/show_bug.cgi?id=490840 Alex Bikadorov changed: What|Removed |Added CC||alex.bikado...@kdemail.net Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #2 from Alex Bikadorov --- *** This bug has been marked as a duplicate of bug 485865 *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 474596] Krusader always crashes after drag-n-drop several files on info bar
https://bugs.kde.org/show_bug.cgi?id=474596 Alex Bikadorov changed: What|Removed |Added CC||alex.bikado...@kdemail.net Status|REPORTED|CONFIRMED Ever confirmed|0 |1 Version|unspecified |Git --- Comment #2 from Alex Bikadorov --- Yes, it crashes :( -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 490603] Krusader drag and drop to fille-count line line causes crash
https://bugs.kde.org/show_bug.cgi?id=490603 Alex Bikadorov changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||alex.bikado...@kdemail.net --- Comment #2 from Alex Bikadorov --- *** This bug has been marked as a duplicate of bug 474596 *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 474596] Krusader always crashes after drag-n-drop several files on info bar
https://bugs.kde.org/show_bug.cgi?id=474596 Alex Bikadorov changed: What|Removed |Added CC||hippost...@gmail.com --- Comment #1 from Alex Bikadorov --- *** Bug 490603 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 448647] Krusader sometimes crashes when copying or moving files
https://bugs.kde.org/show_bug.cgi?id=448647 Alex Bikadorov changed: What|Removed |Added CC||k...@vanwingerde.nl --- Comment #8 from Alex Bikadorov --- *** Bug 471596 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 471596] Crash during copy
https://bugs.kde.org/show_bug.cgi?id=471596 Alex Bikadorov changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||alex.bikado...@kdemail.net --- Comment #1 from Alex Bikadorov --- Duplicate of initial bug reported in 448647 which was fixed with v2.8.0. *** This bug has been marked as a duplicate of bug 448647 *** -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 490477] Internal editor should remember cursor and scroll position for recent files
https://bugs.kde.org/show_bug.cgi?id=490477 Alex Bikadorov changed: What|Removed |Added CC||alex.bikado...@kdemail.net Severity|normal |wishlist -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 476194] sync only changed files no more possible
https://bugs.kde.org/show_bug.cgi?id=476194 --- Comment #7 from Alex Bikadorov --- >I think "Asymmetric" flag is enough to copy from the right and overwrite the >left files. This is not only my opinion, this is how the program should >behave according to the documentation. The documentation could (and should) be adapted. I would still prefer the solution with "Ignore Date" being used. It is safer which was the intention of the https://phabricator.kde.org/D26887 and requires only one click more by the user. But I leave the decision to Toni (see https://invent.kde.org/utilities/krusader/-/merge_requests/138#note_1003388 ) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 488503] KDE Connect Send notifications plugin no longer populates the applications list. Cannot blacklist anything.
https://bugs.kde.org/show_bug.cgi?id=488503 alex <988a...@mail.ru> changed: What|Removed |Added CC||988a...@mail.ru -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490967] some software is slow down my laptop/pc. how to fix them ?
https://bugs.kde.org/show_bug.cgi?id=490967 alex bond changed: What|Removed |Added URL||https://imagecompres.online ||/resize-image-to-20-kb.php -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 490967] New: some software is slow down my laptop/pc. how to fix them ?
https://bugs.kde.org/show_bug.cgi?id=490967 Bug ID: 490967 Summary: some software is slow down my laptop/pc. how to fix them ? Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: felizamocca...@talemarketing.com Target Milestone: --- Hi, I'm having issues with some software slowing down my laptop/PC. Can you help me figure out how to fix it? I've noticed that my device is lagging and not performing as it should. I suspect it's due to some of the programs I've installed. What steps can I take to identify and resolve the problem? Any tips on optimizing my system's performance would be greatly appreciated. Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 357051] KDE Connect fails to detect my PC and my PC fails to detect my Android 6.0 Phone.
https://bugs.kde.org/show_bug.cgi?id=357051 Alex changed: What|Removed |Added CC||vonru...@yahoo.com --- Comment #12 from Alex --- Same issue, in: Arch/Manjaro 6.6.40-1 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 kdeconnect.app: 24.05.2 kdeconnect.daemon: 24.05.2 Fixed by running: killall kdeconnectd mv ~/.config/kdeconnect ~/.config/kdeconnect.bak and re-running kdeconnect-app Seems something might have borked the configuration file this most prior update I did? From KDE Plasma 6.0.3 to 6.0.5? Either way, it's working flawlessly now. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489892] Icons only Taskbar window previews are too sensitive when the cursor leaves them
https://bugs.kde.org/show_bug.cgi?id=489892 --- Comment #8 from Alex --- Created attachment 172047 --> https://bugs.kde.org/attachment.cgi?id=172047&action=edit Example Here is an example for a cursor path that closes the previews as soon as the terminal icon is touched. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489892] Icons only Taskbar window previews are too sensitive when the cursor leaves them
https://bugs.kde.org/show_bug.cgi?id=489892 Alex changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #7 from Alex --- Can it be related to having a vertical panel? The graphic* linked in the other bug also seems to have the triangle the other way round than what my problem is, but maybe here it already flipped. It would be cool if there is any way to visualize the triangle. I'm not even sure how I would construct the triangle when moving from the preview to the taskbar as the taskbar items are no children of the previews and the amazon solution seems to work by assuming a hierarchy. * https://64.media.tumblr.com/53bdf2f4d5b0a7489743e2eaa140cd89/96541d7f363acfd3-e5/s500x750/8896d08ca510f3c71f98e61f729f8b82ea908614.png -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 489892] Icons only Taskbar window previews are too sensitive when the cursor leaves them
https://bugs.kde.org/show_bug.cgi?id=489892 Alex changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Alex --- This time the stupid bot is actually right and I should have already posed it ... here is the info that is still missing: Operating System: Debian GNU/Linux 12 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.115.0 Qt Version: 5.15.13 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 489945] Wayland compositor (sometimes) outputs corrupted video signal to one of two external monitors
https://bugs.kde.org/show_bug.cgi?id=489945 --- Comment #4 from Alex Lowe --- (In reply to Zamundaaa from comment #1) > Does switching to a different tty and back also fix it? OK so more about that with a kernel update and other updates (Qt 6.7.2, kernel 6.8.0-39-generic): I'm no longer getting the corruption - instead I'm getting the monitors not coming out of sleep. Switching to a different TTY and waiting for the monitors to wake up and show the terminal does fix it, but I have to wait for the monitors to show the terminal. This is probably a separate issue so I'll file it as such, but I can no longer reproduce the corruption. -- You are receiving this mail because: You are watching all bug changes.
