[Powerdevil] [Bug 469819] kbd_backlight restored to wrong value after lid close-open
https://bugs.kde.org/show_bug.cgi?id=469819 --- Comment #19 from Toby Fox --- I just tested it on Plasma 6.0.4 and it's working, thanks all! -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465629] Skip empty and comment lines when loading m3u8 playlist
https://bugs.kde.org/show_bug.cgi?id=465629 Toby changed: What|Removed |Added Resolution|--- |FIXED Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465629] Skip empty and comment lines when loading m3u8 playlist
https://bugs.kde.org/show_bug.cgi?id=465629 --- Comment #2 from Toby --- (In reply to Jack Hill from comment #1) > Please can you provide an example file? Just tested again and seems like it has been fixed in the latest release. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 469819] kbd_backlight restored to wrong value after lid close-open
https://bugs.kde.org/show_bug.cgi?id=469819 Toby Fox changed: What|Removed |Added Resolution|FIXED |--- CC||toby...@gmail.com Status|RESOLVED|REOPENED --- Comment #15 from Toby Fox --- I have this issue currently as well, on powerdevil version 6.0.2-3 - started with the update to KDE version 6. It's definitely lid close: if I suspend and wake without lid close, it remembers keyboard brightness correctly. If I suspend, then close lid, then open to wake, it remembers correctly. But if I suspend via closing the lid, when I open it, the keyboard brightness is set to 0. Reopening bug, since when I kill powerdevil (`killall org_kde_powerdevil`) and close then open lid, keyboard backlight remains unchanged. Operating System: Arch Linux KDE Plasma Version: 6.0.2 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 Kernel Version: 6.8.1-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 12 × Intel® Core™ i7-10750H CPU @ 2.60GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics Manufacturer: Dell Inc. Product Name: XPS 17 9700 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482142] drag in drop files in Google Chrome renders Chrome unusable
https://bugs.kde.org/show_bug.cgi?id=482142 Toby Fox changed: What|Removed |Added CC||toby...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482289] Full screen game on single monitor with multi monitor setup. Captured mouse cursor on border triggers wrong event/signal
https://bugs.kde.org/show_bug.cgi?id=482289 Toby changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Toby --- Seems to have been fixed with today's updated packages from Neon. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482239] battlefield V mouse input broken on wayland
https://bugs.kde.org/show_bug.cgi?id=482239 Toby changed: What|Removed |Added CC||torbjorn.nil...@gmail.com --- Comment #1 from Toby --- This may be the same issue I am experiencing: https://bugs.kde.org/show_bug.cgi?id=482289 Will watch your thread in case a KDE developer picks it up. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482289] Full screen game on single monitor with multi monitor setup. Captured mouse cursor on border triggers wrong event/signal
https://bugs.kde.org/show_bug.cgi?id=482289 Toby changed: What|Removed |Added Summary|Full screen game on single |Full screen game on single |monitor with multi monitor |monitor with multi monitor |with mouse capture. Mouse |setup. Captured mouse |cursor on border triggers |cursor on border triggers |wrong event/signal |wrong event/signal -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482289] New: Full screen game on single monitor with multi monitor with mouse capture. Mouse cursor on border triggers wrong event/signal
https://bugs.kde.org/show_bug.cgi?id=482289 Bug ID: 482289 Summary: Full screen game on single monitor with multi monitor with mouse capture. Mouse cursor on border triggers wrong event/signal Classification: Plasma Product: kwin Version: master Platform: Neon OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: torbjorn.nil...@gmail.com Target Milestone: --- Created attachment 166341 --> https://bugs.kde.org/attachment.cgi?id=166341=edit Wayland, Vulkan and KWIN info from Info Center SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** In KDE Plasma 6 on Wayland, with Steam installed STEPS TO REPRODUCE 1. Use multi monitor setup, with main screen in the center (if 3 screens) or on the left (if 2 screens) 2. Launch a full screen game in Steam, f.ex C 3 or Red Alert 3 3. When in a game, move around the map by pushing the mouse cursor towards the bottom or right edge of the screen, while the fullscreen has mouse capture OBSERVED RESULT The map will move in the wrong direction (up or to the left) as if the mouse cursor is sending the wrong signal EXPECTED RESULT The map to move towards the direction where the mouse cursor is touching the border of the screen SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: 6.0 KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Nvidia GTX 1060 graphics card Nvidia Driver: 535.161.07 Distro driver (recommended) on Wayland session -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469777] KWin since 5.27.5 uses 1 CPU core at 100% whenever something is using PipeWire to capture the screen
https://bugs.kde.org/show_bug.cgi?id=469777 --- Comment #17 from toby --- Just tested the fix on Plasma 6.0 RC2 which works for me. I had put up a bug bounty for this on KDE Discuss (https://discuss.kde.org/t/bug-fix-screen-freezing-lags-every-second-when-screen-sharing-wayland/8768) elitedev could you please email me or message me on KDE Discuss to discuss payment. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479207] Applets opening up on the left side
https://bugs.kde.org/show_bug.cgi?id=479207 toby changed: What|Removed |Added CC||to...@sent.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479207] Applets opening up on the left side
https://bugs.kde.org/show_bug.cgi?id=479207 --- Comment #2 from toby --- Created attachment 164565 --> https://bugs.kde.org/attachment.cgi?id=164565=edit hovering over volume shows info on the left side -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479207] Applets opening up on the left side
https://bugs.kde.org/show_bug.cgi?id=479207 --- Comment #1 from toby --- Created attachment 164564 --> https://bugs.kde.org/attachment.cgi?id=164564=edit Edit mode showing panel settings on the left monitor -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 479207] New: Applets opening up on the left side
https://bugs.kde.org/show_bug.cgi?id=479207 Bug ID: 479207 Summary: Applets opening up on the left side Classification: Plasma Product: plasmashell Version: 5.27.10 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Panel Assignee: plasma-b...@kde.org Reporter: to...@sent.com CC: niccolo.venera...@gmail.com Target Milestone: 1.0 Created attachment 164563 --> https://bugs.kde.org/attachment.cgi?id=164563=edit Network applet opening on the left SUMMARY When clicking on any widget that has a popup it will show on the left STEPS TO REPRODUCE 1. Click any widget in panel OBSERVED RESULT Applets open on the left side EXPECTED RESULT Applets should open above the applet. SOFTWARE/OS VERSIONS Operating System: Arch Linux Operating System: Arch Linux KDE Plasma Version: 5.27.10 KDE Frameworks Version: 5.113.0 Qt Version: 5.15.11 Kernel Version: 6.6.8-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X3D 8-Core Processor Memory: 15.5 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7A34 ADDITIONAL INFORMATION I have 2 monitors, 1 main one and another to the left of it. It does not happen when my second monitor is unplugged. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469777] KWin since 5.27.5 uses 1 CPU core at 100% whenever something is using PipeWire to capture the screen
https://bugs.kde.org/show_bug.cgi?id=469777 --- Comment #4 from toby --- (In reply to toby from comment #3) > I've also been having this issue and it's been causing my screen to lag > every time I share my screen. I've now confirm this is the case by reverting commit 226d8c0a3b464f8870c45bfe5079f042a3cd5d67 as I do not experience any stutters. I also do not get 100% CPU usage on on core. Here is the bug report to the stuttering issue https://bugs.kde.org/show_bug.cgi?id=471364. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471364] Sharing window with OBS causes periodic desktop stuttering
https://bugs.kde.org/show_bug.cgi?id=471364 --- Comment #7 from toby --- >From the bug report I mentioned earlier Prajna Sariputra is reverting commit 226d8c0a3b464f8870c45bfe5079f042a3cd5d67 in kwin, I've just done that myself to see if it resolves this issue and from what I can tell I'm not getting any stuttering. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471364] Sharing window with OBS causes periodic desktop stuttering
https://bugs.kde.org/show_bug.cgi?id=471364 toby changed: What|Removed |Added CC||to...@sent.com --- Comment #5 from toby --- deadmeu, is one of you CPU cores pinned at 100% or close to it when you screen share? As I believe this issue is related to https://bugs.kde.org/show_bug.cgi?id=469777 as I get 100% on one core when screen sharing on Plasma, I don't experience this on other Wayland compositors. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 478172] Applets like the application launcher, notifications menu, KRunner, etc. open in the center of the screen
https://bugs.kde.org/show_bug.cgi?id=478172 Toby changed: What|Removed |Added Product|plasmashell |neon CC||torbjorn.nil...@gmail.com Component|general |general Target Milestone|1.0 |--- Version|5.27.10 |unspecified --- Comment #7 from Toby --- I am experiencing this as well. KDE Neon, Plasma 5.27.10, Wayland, Nvidia 535.129.03 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469777] KWin since 5.27.5 uses 1 CPU core at 100% whenever something is using PipeWire to capture the screen
https://bugs.kde.org/show_bug.cgi?id=469777 toby changed: What|Removed |Added CC||to...@sent.com --- Comment #3 from toby --- I've also been having this issue and it's been causing my screen to lag every time I share my screen. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471364] Sharing window with OBS causes periodic desktop stuttering
https://bugs.kde.org/show_bug.cgi?id=471364 toby changed: What|Removed |Added CC||rethinkmanife...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 471364] Sharing window with OBS causes periodic desktop stuttering
https://bugs.kde.org/show_bug.cgi?id=471364 toby changed: What|Removed |Added CC|tobygethi...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460675] blurry screenshot under wayland with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=460675 --- Comment #9 from Toby --- (In reply to Toby from comment #8) > (In reply to Ye Jingchen from comment #4) > > (In reply to Vlad Zahorodnii from comment #3) > > > The reason why screenshots are blurry is that kwin downscales the window > > > contents. 5.27 should be better. Note that the client side should also > > > support fractional scaling. Qt should support fractional scaling in 6.5+ > > > > I think the situation is a bit frustrating even in 5.27, because I still > > can't get a screenshot that looks the same as what is on screen. > > > > My theory is the same as what Toby described initially, that screenshots by > > Spectacle are way blurrier that on screen, not only because window content > > is scaled down (from 2x), but it's *scaled down and up again*, creating > > artifacts not present on screen. > > > > Though I wonder whether this is caused by kwin sending blurry images to > > Spectacle, or Spectacle mess up scaling stuff internally. > > 5.27 worked for me on Fedora KDE. I tested by displaying an image with > single-pixel dots on the screen and taking a screenshot, all dots are > clearly visible and not blurry. I guess it could be a distribution-specific > issue. Or might be related to multi-monitor setups -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460675] blurry screenshot under wayland with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=460675 --- Comment #8 from Toby --- (In reply to Ye Jingchen from comment #4) > (In reply to Vlad Zahorodnii from comment #3) > > The reason why screenshots are blurry is that kwin downscales the window > > contents. 5.27 should be better. Note that the client side should also > > support fractional scaling. Qt should support fractional scaling in 6.5+ > > I think the situation is a bit frustrating even in 5.27, because I still > can't get a screenshot that looks the same as what is on screen. > > My theory is the same as what Toby described initially, that screenshots by > Spectacle are way blurrier that on screen, not only because window content > is scaled down (from 2x), but it's *scaled down and up again*, creating > artifacts not present on screen. > > Though I wonder whether this is caused by kwin sending blurry images to > Spectacle, or Spectacle mess up scaling stuff internally. 5.27 worked for me on Fedora KDE. I tested by displaying an image with single-pixel dots on the screen and taking a screenshot, all dots are clearly visible and not blurry. I guess it could be a distribution-specific issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 460675] blurry screenshot under wayland with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=460675 --- Comment #6 from Toby --- I can confirm that the 5.27 update fixed my issue (Wayland, 1.75 scale, single monitor), so I suggest marking this as solved. The multi-monitor case is more tricky and maybe should have its own separate issue. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 465641] Wrong text encoding for file names in X11
https://bugs.kde.org/show_bug.cgi?id=465641 Toby changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Toby --- Turned out to be some per-user settings messed up the charmap. Solved after deleting all user config files. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 465641] New: Wrong text encoding for file names in X11
https://bugs.kde.org/show_bug.cgi?id=465641 Bug ID: 465641 Summary: Wrong text encoding for file names in X11 Classification: I don't know Product: kde Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: tianer2...@outlook.com Target Milestone: --- SUMMARY Chinese file names become random strings when using the "ls" command and in many other applications. Looks like the encoding is wrong. This only happens in X11, in Wayland, everything worked fine. Many other applications are affected, such as LibreOffice and Python3. LibreOffice displays the file name on its title bar and it becomes a random string. The os.listdir() in Python3 also produce random strings. I guess the system is making wrong assumptions about what encoding those applications use. STEPS TO REPRODUCE 1. create a new folder, cd into it, create a new file named "测试.txt" 2. run ls ./ OBSERVED RESULT the file name becomes "'��'$'\213''��'$'\225''.txt'" EXPECTED RESULT It should not become a random string SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.10-200.fc37.x86_64 (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-9300HF CPU @ 2.40GHz Memory: 7.7 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 465629] New: Does not skip empty and comment lines when loading m3u8 playlist
https://bugs.kde.org/show_bug.cgi?id=465629 Bug ID: 465629 Summary: Does not skip empty and comment lines when loading m3u8 playlist Classification: Applications Product: Elisa Version: 22.12.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: tianer2...@outlook.com Target Milestone: --- SUMMARY Does not skip empty and comment lines in the m3u8 file when loading a playlist STEPS TO REPRODUCE 1. Create a playlist in Elisa, save it to an m3u8 file 2. Open the file in a text editor, add some empty lines and comment lines (lines start with #), save 3. Load the file back, now many invalid entries appear in the playlist entry OBSERVED RESULT Empty lines and comment lines becomes invalid entries. EXPECTED RESULT They should be ignored SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.102.0 Qt Version: 5.15.8 Kernel Version: 6.1.10-200.fc37.x86_64 (64-bit) Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463001] New: Entire system freezes when scaling xwayland window under fractional scaling dpi
https://bugs.kde.org/show_bug.cgi?id=463001 Bug ID: 463001 Summary: Entire system freezes when scaling xwayland window under fractional scaling dpi Classification: Plasma Product: kwin Version: 5.26.4 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: platform-x11-nested Assignee: kwin-bugs-n...@kde.org Reporter: tianer2...@outlook.com Target Milestone: --- Created attachment 154560 --> https://bugs.kde.org/attachment.cgi?id=154560=edit a python opengl helloworld program SUMMARY Entire system freezes when scaling a xwayland window under fractional scaling dpi STEPS TO REPRODUCE 1. Set display scale to 175% in system settings 2. Open any xwayland window 3. Drag to scale the window, trying to make the width very small OBSERVED RESULT Entire system freezes, and I can't switch to other terminals by pressing ctrl+alt+f3, etc. EXPECTED RESULT System still responsive. note: I found it happens mostly when the window title starts to "shrink", i.e. from "A looong title" into "A loo ... g title". If the display scaling factor is integer (100%,200%), it works as expected. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 37 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.100.0 Qt Version: 5.15.7 Kernel Version: 6.0.12-300.fc37.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-1035G4 CPU @ 1.10GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics Manufacturer: Acer Product Name: Spin SP513-54N System Version: V1.10 ADDITIONAL INFORMATION I initially found the problem when running the attached python script. -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 460675] New: blurry screenshot under wayland with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=460675 Bug ID: 460675 Summary: blurry screenshot under wayland with fractional scaling Classification: Applications Product: Spectacle Version: 22.08.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: tianer2...@outlook.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY Under KDE wayland, with fractional scaling, screenshots taken by Spectacle are blurry. STEPS TO REPRODUCE 1. Login using wayland display server (should be default now), set the display scale to 175% 2. Take a screenshot with Spectacle OBSERVED RESULT The screenshot is blurry, like it is being scaled down and up again. EXPECTED RESULT The screenshot should look sharp like what is seen on screen SOFTWARE/OS VERSIONS Operating System: Fedora Linux 36 KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.15-201.fc36.x86_64 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i5-1035G4 CPU @ 1.10GHz Memory: 7.5 GiB of RAM Graphics Processor: Mesa Intel® Iris® Plus Graphics Manufacturer: Acer Product Name: Spin SP513-54N System Version: V1.10 -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 459189] New: KWrite crashes when 3-finger-tap on the text area
https://bugs.kde.org/show_bug.cgi?id=459189 Bug ID: 459189 Summary: KWrite crashes when 3-finger-tap on the text area Product: kate Version: 22.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: kwrite Assignee: kwrite-bugs-n...@kde.org Reporter: tianer2...@outlook.com Target Milestone: --- Application: kwrite (22.04.1) Qt Version: 5.15.5 Frameworks Version: 5.97.0 Operating System: Linux 5.19.8-200.fc36.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 36 (KDE Plasma) DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: As the title says, KWrite crashes every time I do a 3-finger-tap on the text area. The crash can be reproduced every time. -- Backtrace: Application: KWrite (kwrite), signal: Segmentation fault [KCrash Handler] #4 0x7f2135abd259 in QtWaylandClient::QWaylandInputDevice::Touch::touch_frame() () from /lib64/libQt5WaylandClient.so.5 #5 0x7f2133399746 in ffi_call_unix64 () from /lib64/libffi.so.8 #6 0x7f21333964d2 in ffi_call_int.lto_priv () from /lib64/libffi.so.8 #7 0x7f2135a2fe03 in wl_closure_invoke.constprop () from /lib64/libwayland-client.so.0 #8 0x7f2135a30573 in dispatch_event.isra () from /lib64/libwayland-client.so.0 #9 0x7f2135a3073c in wl_display_dispatch_queue_pending () from /lib64/libwayland-client.so.0 #10 0x7f2135ab9615 in QtWaylandClient::QWaylandDisplay::flushRequests() () from /lib64/libQt5WaylandClient.so.5 #11 0x7f21381572b4 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #12 0x7f2138be8d22 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #13 0x7f213812d218 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7f2138130584 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #15 0x7f213817e457 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #16 0x7f2135e16faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #17 0x7f2135e6c2c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #18 0x7f2135e14940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #19 0x7f213817df4a in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #20 0x7f213812bc6a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #21 0x7f2138133d32 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #22 0x563557a7ff05 in main () [Inferior 1 (process 2773) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 362647] Can't search with Chinese characters
https://bugs.kde.org/show_bug.cgi?id=362647 Toby changed: What|Removed |Added CC||tianer2...@outlook.com --- Comment #10 from Toby --- I still encounter this in Fedora36 in 2022. Was the fix merged yet? -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 449119] New: Ask can you cancel cash app payment from the technical team
https://bugs.kde.org/show_bug.cgi?id=449119 Bug ID: 449119 Summary: Ask can you cancel cash app payment from the technical team Product: Active Window Control Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: tobycarte...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Can you cancel the cash app payment? If this is your query then you must speak directly to the tech support team of the cash app. For knowing more about the cash app, you can rely on the expert’s support team. So, feel free to get in touch with the technical team. https://www.emailsupport-contact.com/blog/can-you-cancel-a-pending-cash-app-transaction/ -- You are receiving this mail because: You are watching all bug changes.
[Active Window Control] [Bug 448252] New: Find the solution of Will Cash App refund money if scammed? Issues from tech support
https://bugs.kde.org/show_bug.cgi?id=448252 Bug ID: 448252 Summary: Find the solution of Will Cash App refund money if scammed? Issues from tech support Product: Active Window Control Version: unspecified Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: zrenf...@gmail.com Reporter: tobycarte...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Are you troubling with Will Cash App refund money if scammed? Have you not received a refund yet? Recipient and merchant are not accepting the refund request? In such case, think of choosing reliable customer support service. In addition, the tech support team ensures rectification and diagnosis of the issue. https://www.emailsupport-contact.com/blog/will-cash-app-refund-money-if-scammed/ -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436240] Notification display lag blocks input in Firefox
https://bugs.kde.org/show_bug.cgi?id=436240 --- Comment #9 from Toby Fox --- I have an NVIDIA GeForce GTX 960M GPU (disabled with bbswitch) and Intel HD Graphics 530 iGPU (CPU is Intel i5-6300HQ). I'm also using OpenGL 3.1 and have Automatic in both the Plasma Renderer options. Changing compositor to use OpenGL 2.0 didn't fix the issue for me. However, that did inspire me to check disabling the compositor entirely, and that does fix the issue. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436240] Notification display lag blocks input in Firefox
https://bugs.kde.org/show_bug.cgi?id=436240 Toby Fox changed: What|Removed |Added CC||toby...@gmail.com --- Comment #5 from Toby Fox --- I commented on the other bug, but this one resembles mine more: I have an NVIDIA GPU but it's switched-off and I only use my Intel iGPU. No CPU spike, and just one notification causes it. Doesn't happen only on Firefox for me though, happens with everything. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414785] Notifications cause system lag
https://bugs.kde.org/show_bug.cgi?id=414785 --- Comment #7 from Toby Fox --- I'm having the same issue but with slight variation, not sure if the exact same bug: - Entire UI (kwin? plasma?) freezes for anywhere from 100ms to 1000ms whenever any notification appears - Audio does *not* freeze. Mouse cursor also doesn't freeze, still moves smoothly - I have a dual integrated Intel GPU + NVIDIA GPU (using bbswitch) and my NVIDIA GPU is switched off, so the issue isn't unique to NVIDIA drivers I can reproduce as follows: 1. Open konsole and fill it with enough content such that you can scroll 2. While scrolling up and down with mouse/trackpad, run `notify-send foo` 3. Scrolling freezes for half second when notification appears I tried both triple-buffering and the usleep environment variables for kwin, but no dice. Also tried setting "force lowest latency" in compositor settings, didn't seem to make a difference. Overlays from changing monitor brightness and volume cause the same stutter. It happens only when the overlay first appears: once it's visible I can continue changing the volume without further stutter, and notifications/overlays disappearing do not cause stutter. OS: Arch Linux x86_64 Kernel: 5.12.9-arch1-1 CPU: Intel i5-6300HQ (4) @ 3.200GHz GPU: Intel HD Graphics 530 GPU: NVIDIA GeForce GTX 960M (disabled) KDE Plasma/KWin: 5.22.0 KDE Frameworks: 5.82.0 Qt: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422310] Notifications Cause Youtube Videos and Other Programs To Stutter
https://bugs.kde.org/show_bug.cgi?id=422310 Toby Fox changed: What|Removed |Added CC|toby...@gmail.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 414785] Notifications cause system lag
https://bugs.kde.org/show_bug.cgi?id=414785 Toby Fox changed: What|Removed |Added CC||toby...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422310] Notifications Cause Youtube Videos and Other Programs To Stutter
https://bugs.kde.org/show_bug.cgi?id=422310 Toby Fox changed: What|Removed |Added CC||toby...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 428988] New: The previous brush shortcut only works if the cursor is moving
https://bugs.kde.org/show_bug.cgi?id=428988 Bug ID: 428988 Summary: The previous brush shortcut only works if the cursor is moving Product: krita Version: 4.4.1 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: tobywills...@gmail.com Target Milestone: --- SUMMARY The previous brush shortcut only works when the cursor is moving on an active canvas I made sure the custom shortcut had no conflicts, To test I used key '7' on the keyboard not the keypad. STEPS TO REPRODUCE 1. make or open a canvas 2. select a brush then select another brush so you can switch between them 3. move the cursor over the canvas 4. then without moving your mouse or tablet pen on the canvas use the previous brush shortcut 5. the brush does not switch to the previous one but the brushes docker shows the switch between the brushes 6. now keep the cursor moving on the canvas and use the previous brush shortcut 7. the shortcut works and the brushes change from one to the other as expected OBSERVED RESULT the previous brush shortcut only works when the cursor is moving on the active canvas However the brush switch is shown in the docker as expected EXPECTED RESULT the previous brush shortcut should work when the canvas is active and the cursor is moving or stationary. 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 428249] previous brush shortcut no longer works
https://bugs.kde.org/show_bug.cgi?id=428249 --- Comment #4 from Toby --- Yep it can be resolved now as not a bug unless you have conflicting custom shortcuts Kind regards Toby Willsmer | Illustrator Based in Wellington, New Zealand [image: Logo] <http://www.willsmer.com> e:tobywills...@gmail.com w:willsmer.com <http://www.willsmer.com> s:instagram/tobywillsmer <https://www.instagram.com/tobywillsmer> On Thu, 29 Oct 2020 at 06:36, Ahab Greybeard wrote: > https://bugs.kde.org/show_bug.cgi?id=428249 > > Ahab Greybeard changed: > >What|Removed |Added > > > CC| > |ahab.greybe...@hotmail.co.u >||k > > --- Comment #3 from Ahab Greybeard --- > So, should this be Resolved, Not a Bug? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 428249] previous brush shortcut no longer works
https://bugs.kde.org/show_bug.cgi?id=428249 --- Comment #2 from Toby --- (In reply to Lynx3d from comment #1) > While I can confirm this when setting "Switch to Previous Preset" to > "Return", this is somewhat expected, because by default "Return" is already > bound to "Confirm" in Canvas Input Settings => Tool Invocation. > > I'm not sure why it worked before, it may be a change introduced by fixing > bug 409613, but I'm inclined to say that it never should have worked in the > first place, because that means one key press potentially triggers two > unrelated actions. > > Resolve the key binding conflict, and it should work as expected, at least > it does for me. Ah yep, changed it and it's ok. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 428249] New: previous brush shortcut no longer works
https://bugs.kde.org/show_bug.cgi?id=428249 Bug ID: 428249 Summary: previous brush shortcut no longer works Product: krita Version: 4.4.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Shortcuts and Canvas Input Settings Assignee: krita-bugs-n...@kde.org Reporter: tobywills...@gmail.com Target Milestone: --- SUMMARY the previous brush shortcut no longer works once you start to paint, it only works when you are changing brushes in the docker. I have the previous brush shortcut set to a custom key, the return key. This works as normal in all versions under krita-4.3.0-x86_64.appimage but not in the latest version 4.4.0 STEPS TO REPRODUCE 1. Open a new file 2. select a brush in the docker 3. then select a different brush in the docker 4. keep the cursor in the docker area and before painting anything use the previous brush shortcut 5. This works as expected 6. now paint something on the canvas 7. then try the previous brush shortcut again 8. the shortcut does not work whilst the canvas is actively being painted on OBSERVED RESULT The previous brush shortcut only works if you select brushes in the brushes docker. Once painting, it no longer works unless you switch brushes again in the docker. EXPECTED RESULT The previous brush shortcut should switch between the latest brush and the previous one whilst painting SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 18.0.4 (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.
[gwenview] [Bug 305072] Animated GIF is some milliseconds too slow
https://bugs.kde.org/show_bug.cgi?id=305072 Toby Fox changed: What|Removed |Added CC||toby...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 277996] Make it possible to adjust JPEG quality/compression settings when saving
https://bugs.kde.org/show_bug.cgi?id=277996 --- Comment #22 from Toby Fox --- Yo @Nate Graham you should claim your bounty on https://www.bountysource.com/issues/78105774-make-it-possible-to-adjust-jpeg-quality-compression-settings-when-saving -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 277996] Make it possible to adjust JPEG quality/compression settings when saving
https://bugs.kde.org/show_bug.cgi?id=277996 --- Comment #8 from Toby Fox --- This seems like a good opportunity for me to try out Bountysource! https://www.bountysource.com/issues/78105774-make-it-possible-to-adjust-jpeg-quality-compression-settings-when-saving -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 116617] Please add Extended Attribute support (setxattr, getxattr)
https://bugs.kde.org/show_bug.cgi?id=116617 Toby Fox changed: What|Removed |Added CC||toby...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 277996] Make it possible to adjust JPEG quality/compression settings when saving
https://bugs.kde.org/show_bug.cgi?id=277996 --- Comment #6 from Toby Fox --- Small note that ideally there could be a default setting accessible in preferences, because if you're doing a regular Save (instead of Save As) then there's no dialog with which to give the user the opportunity to change this value. Also, my two cents that this is pretty important! The default value of 75% (what I've seen reported elsewhere, can't confirm that's the current value) is low - any enthusiast using Gwenview to make changes is inadvertently mangling their collection a little bit. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 277996] Make it possible to adjust JPEG quality/compression settings when saving
https://bugs.kde.org/show_bug.cgi?id=277996 Toby Fox changed: What|Removed |Added CC||toby...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410055] filter layer and filter mask pop ups are locked to the center of the screen with dark opaque screen overlay
https://bugs.kde.org/show_bug.cgi?id=410055 --- Comment #5 from Toby --- it's the default GNOME 3 for 18.0.4 desktop -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410055] filter layer and filter mask pop ups are locked to the center of the screen with dark opaque screen overlay
https://bugs.kde.org/show_bug.cgi?id=410055 --- Comment #2 from Toby --- (In reply to vanyossi from comment #1) > Hi! > > Im sorry but this is not a bug in krita but a behaviour on your window > manager. Try to see if you can disable dark overlay for popup windows system > wise. > > Im using xfce and macOs and none of them have that problem, o Kde by default > the parent modal dialogs darken the background. To disable: > > - KDE Settings > Desktop Effects > Dialog Parent: disable > - Apply > > On KDE by default it is possible to move the window, so to move a modal > window you will need to move something else in your system preferences. What > desktop environment are you using? > > Disabling this might be a little different on other desktop environments. Not sure this is the case for Linux users as this issue is only for these two specific layer types. I'm running Ubuntu 18.0.4 and I can run the v4.2.1 app image and everything works as normal. It's any app image version after that the issue has become a problem. For pretty much all the other pop up windows in Krita they are fine, it's these two layer types that have changed since v4.2.1. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 410055] New: filter layer and filter mask pop ups are locked to the center of the screen with dark opaque screen overlay
https://bugs.kde.org/show_bug.cgi?id=410055 Bug ID: 410055 Summary: filter layer and filter mask pop ups are locked to the center of the screen with dark opaque screen overlay Product: krita Version: 4.2.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Filter Layers Assignee: krita-bugs-n...@kde.org Reporter: tobywills...@gmail.com Target Milestone: --- SUMMARY The filter layer and filter mask layers pop ups are locked centrally to the screen and have a dark opaque screen overlay that hinders any accurate colour adjustments being made due to the dark overlay. Versions: It's worth noting that v4.2.1 works as I expect with no overlay and the pop ups being moveable with click and drag. All versions after v4.2.1 have the locked position and screen overlay problem The overlay problem is similar to Bug 384870 but it's not environmental as the v4.2.1 version works fine along side the newer versions (v4.2.2 & v4.2.3) that do not STEPS TO REPRODUCE 1. open or create a file with a normal drawing layer 2. use the small '+' icon in the layer docker to create either a filter layer or a filter mask on the drawing layer 3. the popup and overlay appear OBSERVED RESULT The popup appears and is not moveable from the center position with click and drag. When trying to move it by click and drag the whole app shrinks and moves on drag When the pop up is visible the whole screen has the dark opaque overlay, this makes any colour changes (i.e saturation) from within the filter layer pop ups hard as you cannot accurately see what the changing colours are due to the dark overlay. This is also happening when you go to edit either an existing filter layer or mask layer but this happens in all the mentioned versions here EXPECTED RESULT the popup windows should to be moveable around the screen on click and drag with no dark screen overlay. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubunutu 18.04.2 LTS (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 409968] Text tool gives abort message pop up when trying to edit existing text
https://bugs.kde.org/show_bug.cgi?id=409968 --- Comment #7 from Toby --- Created attachment 121652 --> https://bugs.kde.org/attachment.cgi?id=121652=edit try to save file after pop up has been dismissed -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409968] Text tool gives abort message pop up when trying to edit existing text
https://bugs.kde.org/show_bug.cgi?id=409968 --- Comment #6 from Toby --- (In reply to Tymond from comment #4) > When I pressed Ignore, it appeared right afterwards again - maybe after one > more action, and it didn't have an end - Krita had to be restarted (I > *guess* there was an possibility to save the image, but since those error > messages was really disrupting and happens one after another, it is possible > that the user may not be able to do so). Yes I get the same, if I click 'ignore'the message goes away but then if I click anything it comes back, this then happens all the time until I close Krita and reopen it. If I dismiss the pop up and then click 'File' to try to save the image I get 2 popups with the same message (attached screenshot) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409968] Text tool gives abort message pop up when trying to edit existing text
https://bugs.kde.org/show_bug.cgi?id=409968 --- Comment #2 from Toby --- (In reply to Boudewijn Rempt from comment #1) > Can you consistently reproduce the issue with those steps? I am not getting > that warning. Yes, it happens every time. It doesn't happen in 4.2.2. I also downloaded a fresh version of 4.2.3 to see if it was that and yep it did the same error. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409968] New: Text tool gives abort message pop up when trying to edit existing text
https://bugs.kde.org/show_bug.cgi?id=409968 Bug ID: 409968 Summary: Text tool gives abort message pop up when trying to edit existing text Product: krita Version: 4.2.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: tobywills...@gmail.com Target Milestone: --- Created attachment 121617 --> https://bugs.kde.org/attachment.cgi?id=121617=edit Screenshot with abort popup SUMMARY STEPS TO REPRODUCE 1. open an existing file or make a new one 2. click the text tool 'T' in the toolbar 3. enter some text in the pop up box, click save then click close 4. click the text tool 'T' in the toolbar 5. now go to try and edit the newly added text OBSERVED RESULT the text pop up appears along with an error message pop up saying abort or ignore. Clicking abort closes Krita and ignore does just that but every time you try to edit text this pop up message appears Krita has encountered an internal error: SAFE ASSERT (krita): "!m_d->readyShortcut" in file /home/appimage/workspace/Krita_Release_Appimage_Build/krita/libs/ui/input/kis_shortcut_matcher.cpp, line 579 Please report a bug to developers! Press Ignore to try to continue. Press Abort to see developers information (all unsaved data will be lost) EXPECTED RESULT should be able to edit and save text with no error message pop up SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Ubuntu 18.0.4.2 (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.
[dolphin] [Bug 388660] Feature Request: Increase max icon thumbnail size
https://bugs.kde.org/show_bug.cgi?id=388660 --- Comment #7 from Toby Fox <toby...@gmail.com> --- Created attachment 109998 --> https://bugs.kde.org/attachment.cgi?id=109998=edit Dolphin thumbnails correctly scaled 2x on 3840x2160 display (In reply to Nate Graham from comment #6) > IMHO a change to the FDO spec would indeed be worthwhile. 256px isn't really > that big anymore on today's displays. > > Toby, can you re-log-in/reboot and see if that fixes things for you? Ok, this is interesting! In my previous screenshot, I pulled up the display settings but didn't change them: I had it set at 2x scale for many months. However, I tried changing scaling to 3x, rebooted, changed scaling back to 2x and rebooted again, and now my thumbnails are showing larger as intended - 512px at max. Looks like previously the plasma UI and most applications were correctly scaled for me at 2x, but some applications (dolphin, konsole, maybe others) were stuck at 1x and needed settings to be changed and rebooted to get it to work. Maybe there was some HiDPI-related Dolphin or KDE update a while back that didn't apply properly without this. Anyway, screenshot attached of the it "correctly" scaled at 2x. Now of course the issue is we have a 256px thumbnail upscaled to 512px, so it looks blurry, and the other issues mentioned by Henrik. Situation is a little better, but I definitely think it's worth pursuing further. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 388660] Feature Request: Increase max icon thumbnail size
https://bugs.kde.org/show_bug.cgi?id=388660 --- Comment #3 from Toby Fox <toby...@gmail.com> --- Created attachment 109740 --> https://bugs.kde.org/attachment.cgi?id=109740=edit Screenshot showing 2x scaled display settings and 256px dolphin thumbnails (In reply to Kai Uwe Broulik from comment #2) > Do you have screen scaling enabled? If you set it to 2x scaling, the "256px" > should actually become 512. (The thumbnails themselves don't support that, > though, so they'd be larger but blurry. Fixing that would require serious > re-engineering in the thumbnailer) Interesting - my screen scaling is set to 2x, and thumbnail size maxed out, but it does seem like they're still 256px. See attached screenshot - there are 5 rows, and even without padding or dolphin UI, that would be 5*512px = 2560px, greater than my vertical resolution of 2160px. And the dolphin UI (and all UI elements in my desktop environment) are appropriately scaled - if scaled larger they'd be too big. I understand, however, especially from Rog131's helpful reply, how deep this functionality runs and how dependent it is on other standards and packages, so I see it would be a laborious change. But I do think that as resolutions get ever bigger and devices more multi-purpose and media-heavy, such a change to the whole ecosystem is (hopefully) due eventually. But I imagine this is isn't in the hands of the Dolphin team or even KDE. It's a bummer though. I've tried Gwenview, DigiKam, and several other pieces of software, and so far nothing has this relatively basic (from a user's perspective) functionality :( -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 388660] Feature Request: Increase max icon thumbnail size
https://bugs.kde.org/show_bug.cgi?id=388660 Toby Fox <toby...@gmail.com> changed: What|Removed |Added CC| |toby...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 388660] New: Feature Request: Increase max icon thumbnail size
https://bugs.kde.org/show_bug.cgi?id=388660 Bug ID: 388660 Summary: Feature Request: Increase max icon thumbnail size Product: dolphin Version: unspecified Platform: Archlinux Packages OS: Linux Status: UNCONFIRMED Severity: wishlist Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: toby...@gmail.com Target Milestone: --- Currently the max thumbnail size is 256px. My screen's resolution is 3840x2160, so the largest I can get is approx 5 rows x 8 columns. For a folder of images, sometimes I want to preview multiple images at once at a larger size without switching to another application. I'd suggest 512px or even 1024px. I think this would have minimal impact on users who don't care about this feature (the only thing I can think of is that it would increase the granularity of the icon size slider in the status bar) but would be quite helpful for others. I'm not sure if this is related to any HiDPI issues, but the interface is otherwise scaled normally for me. Regardless, even if some upcoming HiDPI changes increased the preview size, I imagine plenty of users would want still larger sizes. -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 352346] Description and options for Hunyango and Haenau wallpaper types are missing
https://bugs.kde.org/show_bug.cgi?id=352346 Toby Fox <toby...@gmail.com> changed: What|Removed |Added CC| |toby...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 341143] Wallpaper on every desktop is gone.
https://bugs.kde.org/show_bug.cgi?id=341143 Toby Fox <toby...@gmail.com> changed: What|Removed |Added CC| |toby...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 346689] Unused Desktop Sessions appear when switching users
https://bugs.kde.org/show_bug.cgi?id=346689 --- Comment #3 from Toby Newman <k...@asktoby.com> --- Just updated to Fedora 23 KDE spin yesterday. I'm running kf5-plasma.x86_64 5.17.0-3.fc23. Not caught up to 5.2/.3 yet, will report back when I do. -- You are receiving this mail because: You are watching all bug changes.
