[dolphin] [Bug 488752] New: Dolphin fails to connect to remote server via SFTP with ed25519-sk key
https://bugs.kde.org/show_bug.cgi?id=488752 Bug ID: 488752 Summary: Dolphin fails to connect to remote server via SFTP with ed25519-sk key Classification: Applications Product: dolphin Version: 24.05.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: bars: location Assignee: dolphin-bugs-n...@kde.org Reporter: tyler.gaut...@linuxdragon.dev CC: kfm-de...@kde.org Target Milestone: --- Created attachment 170646 --> https://bugs.kde.org/attachment.cgi?id=170646&action=edit Dolphin SFTP logs *** 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. Create an SSH key pair of ed25519-sk type. You'll need a hardware security key. 2. Upload public key to remote device. 3. Disable SSH password authentication on the remote device. 4. Insert hardware security key registered with the SSH key pair. 5. Connect to the remote device by entering sftp://remote_device_ip_address in the location bar of Dolphin. In my case, remote device has the same username as the client; so there is no need to provide a username. OBSERVED RESULT A red banner appears in Dolphin with the text "Authentication failed." EXPECTED RESULT Dolphin prompts for the user to confirm user presence. With the key. User touches the security key, and is logged into the graphical SFTP session. SOFTWARE/OS VERSIONS Windows: N/A macOS: N/A Linux/KDE Plasma: Fedora Linux 40 (available in About System) KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.3.0 Qt Version: 6.7.1 ADDITIONAL INFORMATION I first reported this issue on the forum: https://discuss.kde.org/t/sftp-authentication-fails-on-dolphin/7770. (Please note, at the time, I was still running Plasma 5.) Today, I ran Dolphin again with the command suggested by luisbocanegra in the second post, `KIO_SFTP_LOG_VERBOSITY=10 KDE_FORK_SLAVES=1 QT_LOGGING_RULES="log_kio_sftp=true;kf.kio.workers.sftp=true;" dolphin --new-window sftp://192.168.57.3`. I've attached the output in a text file. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403563] Memory leak in plasma desktop (plasmashell)
https://bugs.kde.org/show_bug.cgi?id=403563 --- Comment #25 from Tyler Pennington --- Also, to the people looking at this and thinking "who cares, no one uses slideshow anyway", please consider the fact that OLED displays are rapidly becoming the standard display panel type on virtually all personal devices. Some sort of wallpaper slideshow or animated wallpaper is the most responsible way to use a wallpaper and minimize OLED burn-in over time. Until this bug is fixed I feel my only option is to use a pure black background. This is a pretty minor inconvenience but obviously quite annoying. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 403563] Memory leak in plasma desktop (plasmashell)
https://bugs.kde.org/show_bug.cgi?id=403563 Tyler Pennington changed: What|Removed |Added CC||tyler...@gmail.com --- Comment #23 from Tyler Pennington --- This bug still exists in plasma 6.0 (and current plasma 6.1 preview). I have observed this bug on both fedora and arch linux, going back at least 3 years. Interestingly I believe this bug is only affecting NVIDIA; I experience this memory leak with my RTX 4090 (and previous 3090) but not with an AMD 7900XTX. All three GPUs were tested with the same mobo/cpu/ram -- the CPU is an AMD 7800X3D. I have not tested if this leak occurs when using open source NVIDIA drivers, I have only used the proprietary drivers. However I believe it is a KDE bug and not an NVIDIA bug because I do not have similar memory leaks with GNOME or other wayland compositors (e.g. hyprland using swww wallpaper utility) regardless of GPU used. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 --- Comment #43 from Tyler Duzan --- Just updated my system and can confirm this is now fixed. Thank you all. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 --- Comment #38 from Tyler Duzan --- I'm waiting for 6.0.5 to be available in Arch, and then I will confirm the fix in a comment here. Thanks for the rapid resolution! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] With fractional scale, bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 --- Comment #23 from Tyler Duzan --- Just updating this to say I'm now on Plasma 6.0.3, QT 6.7.0, and still on KDE Framework 6.0.0. The behavior remains the same. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] Bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 --- Comment #11 from Tyler Duzan --- Just wanted to update and confirm that by setting my scale factor to 160%, this makes the erroneous behavior noted in this bug go away. The 150% scale factor is the default, however, so this behavior occurs with the default settings. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] Bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 --- Comment #7 from Tyler Duzan --- I updated to 6.0.2 Plasma today with an updated microcode and firmware package for AMD devices. The same erroneous behavior is persisting, however. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] Bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 Tyler Duzan changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Tyler Duzan --- This is a Framework 13 AMD laptop with a Ryzen 7 7840U which has a Radeon 780M GPU, on the internal display which is a 2256x1504 display I am running at 150% scaling, which is the default setting. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] Bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 Tyler Duzan changed: What|Removed |Added CC||tris...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] Bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 --- Comment #1 from Tyler Duzan --- Created attachment 166797 --> https://bugs.kde.org/attachment.cgi?id=166797&action=edit Video of the bug taken from iPhone showing the color shifting behavior This attachment is a video taken from my iPhone of the color shifting behavior as I move my mouse. As I move my mouse you can see the pixels slightly shift colors back and forth. The video is 9 seconds long and has been re-encoded using Handbrake and resized to 720p for size. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482987] New: Bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows
https://bugs.kde.org/show_bug.cgi?id=482987 Bug ID: 482987 Summary: Bottom edge of screen has pixels that are held to the color of previously opened windows after closing those windows Classification: Plasma Product: kwin Version: 6.0.1 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: tris...@gmail.com Target Milestone: --- Created attachment 166795 --> https://bugs.kde.org/attachment.cgi?id=166795&action=edit Screenshot showing the pixel line w/ Firefox open 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 *** First of all, I'm not certain I'm reporting this against the right product and component, I was unsure how to trace it specifically. If I have some guidance on tracing this issue, I am happy to work with anyone in order to get more specific and confirm the impacted product/component. I updated to 6.0.1 and noticed this issue almost immediately. I originally had thought my laptop screen might be getting pixels stuck or there was something going on with the new floating taskbar. I rebooted the system and verified that this is not present on a fresh boot after login, it's only after opening any application (for example, firefox) that the pixels start showing. The color seems to be related to the colors present in the logo/icon on the taskbar of the application but not exactly. It's possible to screenshot, so confirmed to not be a local hardware issue. This issue is best seen visually, but essentially the very last row of my display has a series of pixels in a thin line that hold a color from a prior window, even though that window didn't extend visibly below the taskbar. The pixels also shift in color as I type or take other actions. This only happens since I upgrade to 6.0.1, and I am using Wayland. I will attach both a screenshot and a video taken from my phone camera showing the color shift behavior. As it shows up in screenshots, it's clear that it's not something physical involving my hardware. STEPS TO REPRODUCE 1. Start your computer and login to Plasma 6 desktop from the Login manager 2. Open any application in your taskbar 3. Wait a few moments 4. Pixel lines will appear on the bottom edge, not always in the same position but generally towards the left side of the screen. OBSERVED RESULT See the screenshot EXPECTED RESULT There should be no extraneous pixel line on the bottom of the display. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux w/ 6.7.9-arch1-1 kernel and kwin 6.0.1-1 (available in About System) KDE Plasma Version: 6.0.1 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION See attached screenshots -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 481685] New: Plasma Crashes when I turn on the computer first, then turn on my monitors
https://bugs.kde.org/show_bug.cgi?id=481685 Bug ID: 481685 Summary: Plasma Crashes when I turn on the computer first, then turn on my monitors Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: coldresplende...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.6.11-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: A bit of preamble. I was sleeping the computer, then turned it on, which was fine. I assume this was because my twin monitors were still on as well. I did this around 3 to 4 times with no issue. However, this last time, i suspended (sleep) my computer then turned off my twin monitors. When I woke up the computer, I forgot to turn them on before I woke it. When the monitors finally turned on, I was greeted with this Plasma has crashed error. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7ff78e0d85cc in QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #5 0x7ff797b8254d in QOpenGLContext::create() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #6 0x7ff7994079d0 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7ff799409b35 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7ff79940a46f in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7ff7974cbd43 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7ff7972a8134 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #11 0x7ff7973287dc in ?? () from /lib/x86_64-linux-gnu/libc.so.6 Thread 9 (Thread 0x7ff73e4d66c0 (LWP 3668) "KCupsConnection"): #1 0x7ff796119c9f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff7960ca4c5 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff7960ca958 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7ff7960caacc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7ff79770984e in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff7976b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7ff7974cab87 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff73d816667 in KCupsConnection::run() () from /lib/x86_64-linux-gnu/libkcupslib.so #9 0x7ff7974cbd43 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7ff7972a8134 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #11 0x7ff7973287dc in ?? () from /lib/x86_64-linux-gnu/libc.so.6 Thread 8 (Thread 0x7ff73ee656c0 (LWP 3661) "plasmashell"): #1 0x7ff79526ca62 in ?? () from /lib/x86_64-linux-gnu/libusbmuxd-2.0.so.6 #2 0x7ff79526de60 in ?? () from /lib/x86_64-linux-gnu/libusbmuxd-2.0.so.6 #3 0x7ff7972a8134 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #4 0x7ff7973287dc in ?? () from /lib/x86_64-linux-gnu/libc.so.6 Thread 7 (Thread 0x7ff763ffe6c0 (LWP 3651) "QQuickPixmapRea"): #1 0x7ff7960ca9ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7ff7960caacc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7ff79770984e in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7ff7976b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7ff7974cab87 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7ff7993566d6 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7ff7974cbd43 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7ff7972a8134 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x7ff7973287dc in ?? () from /lib/x86_64-linux-gnu/libc.so.6 Thread 6 (Thread 0x7ff76ff456c0 (LWP 3641) "CPMMListener"): #1 0x7ff786872a57 in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.525.147.05 #2 0x7ff78687034a in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.525.147.05 #3 0x7ff7972a8134 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #4 0x7ff7973287dc in ?? () from /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7ff775d036c0 (LWP 3640) "QSGRenderThread"): #1 0x7ff7972a7558 in pthread_cond_wait () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7ff7974d1a2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.s
[plasmashell] [Bug 481022] New: Plasma crashed when woken from a suspended state
https://bugs.kde.org/show_bug.cgi?id=481022 Bug ID: 481022 Summary: Plasma crashed when woken from a suspended state Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian stable OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: coldresplende...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.5) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.5.0-1mx-ahs-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.5 [KCrashBackend] -- Information about the crash: I hibernated my computer, then after around 12 hours I decided to wake it up. I only saw the crash notice when I looked at the computer. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7fbeac965624 in QScreen::handle() const () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #5 0x7fbea2ed8598 in QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () from /lib/x86_64-linux-gnu/libQt5XcbQpa.so.5 #6 0x7fbeac98254d in QOpenGLContext::create() () from /lib/x86_64-linux-gnu/libQt5Gui.so.5 #7 0x7fbeae2079d0 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fbeae209b35 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7fbeae20a46f in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #10 0x7fbeac2cbd43 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fbeac0a8134 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #12 0x7fbeac1287dc in ?? () from /lib/x86_64-linux-gnu/libc.so.6 Thread 6 (Thread 0x7fbe43fff6c0 (LWP 3525) "CPMMListener"): #1 0x7fbe9a8dadee in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.525.147.05 #2 0x7fbe9a872698 in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.525.147.05 #3 0x7fbe9a872a6a in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.525.147.05 #4 0x7fbe9a87034a in ?? () from /lib/x86_64-linux-gnu/libnvidia-glcore.so.525.147.05 #5 0x7fbeac0a8134 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #6 0x7fbeac1287dc in ?? () from /lib/x86_64-linux-gnu/libc.so.6 Thread 5 (Thread 0x7fbe8aed56c0 (LWP 3509) "QSGRenderThread"): #1 0x7fbeac0a7558 in pthread_cond_wait () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7fbeac2d1a2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fbeae208085 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7fbeae20a4b1 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fbeac2cbd43 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fbeac0a8134 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #7 0x7fbeac1287dc in ?? () from /lib/x86_64-linux-gnu/libc.so.6 Thread 4 (Thread 0x7fbe993ff6c0 (LWP 3467) "QQmlThread"): #1 0x7fbeaaf029ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbeaaf02acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbeac50984e in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fbeac4b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fbeac2cab87 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fbeadd28555 in ?? () from /lib/x86_64-linux-gnu/libQt5Qml.so.5 #7 0x7fbeac2cbd43 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fbeac0a8134 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x7fbeac1287dc in ?? () from /lib/x86_64-linux-gnu/libc.so.6 Thread 3 (Thread 0x7fbea17966c0 (LWP 3449) "QDBusConnection"): #1 0x7fbeaaf51c9f in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fbeaaf024c5 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fbeaaf02958 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fbeaaf02acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fbeac50984e in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fbeac4b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fbeac2cab87 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fbead069487 in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #9 0x7fbeac2cbd43 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fbeac0a8134 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #11 0x7fbeac1287dc in ?? () from /lib/x86_64-linux-gnu/libc.so.6 Thread 2 (Thread 0x7fbea2bff6c0 (LWP 3329) "QXcbEventQueue"): #1 0x7fbeae947d12
[kate] [Bug 475011] New: Codeview does not open up when restoring from saved session
https://bugs.kde.org/show_bug.cgi?id=475011 Bug ID: 475011 Summary: Codeview does not open up when restoring from saved session Classification: Applications Product: kate Version: 23.08.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: sessions Assignee: kwrite-bugs-n...@kde.org Reporter: ty...@blackcentipede.com Target Milestone: --- Created attachment 161946 --> https://bugs.kde.org/attachment.cgi?id=161946&action=edit Missing Codeview for Split Pane SUMMARY *** When restoring from saved session on Kate, it sometime does not open up the code view, requiring that I close all files on split pane and reopen them. *** STEPS TO REPRODUCE 1. Start Kate 2. Open Saved Session 3. See missing code view for split pane SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.5.5-arch1-1 (64-bit) / Plasma 5.27.8-1 (Provided by Arch Linux Pacman) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.10 Screenshot: -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 474637] New: Cannot add EWS email due to Duo Mobile authenticator
https://bugs.kde.org/show_bug.cgi?id=474637 Bug ID: 474637 Summary: Cannot add EWS email due to Duo Mobile authenticator Classification: Applications Product: kmail2 Version: 5.23.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: config dialog Assignee: kdepim-b...@kde.org Reporter: tylerw...@posteo.net Target Milestone: --- SUMMARY I am trying to add my college's Office365 Exchange email account by following the instructions found here: https://userbase.kde.org/Kmail/Configuring_Kmail/Accounts/Office_365. I am unable to add the account due to Duo Mobile authentication, claiming that the Android version that I am running is too out of date and that I must update it. I can use Duo authentication just fine on this device on other browsers, making me think this is an issue with whatever KMail is using to render the web sign-in system. STEPS TO REPRODUCE 1. Go to add a "Custom Account" 2. Select "EWS" 3. Put in email address to add and select "OAuth2 (Office 365) 4. Add in EWS url "https://outlook.office365.com/ews/exchange.asmx"; 5. Sign in OBSERVED RESULT Cannot authenticate with DUO Mobile due to "outdated Android version" EXPECTED RESULT Be able to authenticate SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Linux Asahi Remix 38 (available in About System) KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.109.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION I can add this email to other clients such as Thunderbird without issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 450301] On KWin 5.24 X11 Nvidia, when reenabling compositing, windows begin flickering and flipping upside-down
https://bugs.kde.org/show_bug.cgi?id=450301 --- Comment #14 from Tyler Harrison --- (In reply to ghoste from comment #11) > I had this issue with Plasma 5.25 and maybe 5.24, but I think it stopped > happening after upgrading to Plasma 5.26. I'm now running Plasma 5.27.2 and > was unable to reproduce it after disabling and re-enabling the compositor 10 > times in X11. Using NVIDIA driver 525.89.02. Unfortunately I am using Plasma 5.27.2 and was able to reproduce this problem (https://bugs.kde.org/show_bug.cgi?id=469809). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 469809] New: Plasma shell flickers and renders some windows upside down after login, followed by crashing
https://bugs.kde.org/show_bug.cgi?id=469809 Bug ID: 469809 Summary: Plasma shell flickers and renders some windows upside down after login, followed by crashing Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Debian testing OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: tyleraharri...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.27.2) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.0-7-amd64 x86_64 Windowing System: X11 Distribution: Debian GNU/Linux 12 (bookworm) DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: The KDE desktop flickers like crazy on all 3 of my monitors after waking up my PC and logging in. Sometimes this flicker will happen until I close certain windows, I believe closing Dolphin usually fixes it. Sometimes it will flicker and then crash itself and flicker a little bit after restarting as well. Windows (usually Konsole) like to render themselves upside down after I wake from sleep and login as well. Highlighting text in Konsole renders the text itself right-side up on an upside down background haha. I'm running Debian testing (bookworm) with the Nvidia 525.89.02 drivers and CUDA 12.0. I don't have any other graphical issues, gaming works just fine. The crash can be reproduced sometimes. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [KCrash Handler] #4 0x7fac643be3d0 in QSGAreaAllocator::deallocateInNode(QPoint const&, QSGAreaAllocatorNode*) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fac643be446 in QSGAreaAllocator::deallocate(QRect const&) () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fac643c4997 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fac643c4acc in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #8 0x7fac643c4ae9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #9 0x7fac4fe53e0d in ?? () from /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/plasma/core/libcorebindingsplugin.so #10 0x7fac6440e44a in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #11 0x7fac6440802f in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #12 0x7fac6440a4b1 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #13 0x7fac624cbd43 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7fac622a7fd4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #15 0x7fac6232866c in ?? () from /lib/x86_64-linux-gnu/libc.so.6 Thread 10 (Thread 0x7fabf6bfd6c0 (LWP 493258) "KCupsConnection"): #1 0x7fac611b59ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fac611b5acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fac6270984e in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fac626b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fac624cab87 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fabf440a667 in KCupsConnection::run() () from /lib/x86_64-linux-gnu/libkcupslib.so #7 0x7fac624cbd43 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fac622a7fd4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x7fac6232866c in ?? () from /lib/x86_64-linux-gnu/libc.so.6 Thread 9 (Thread 0x7fabf73fe6c0 (LWP 493251) "plasmashell"): #1 0x7fac6037ba62 in ?? () from /lib/x86_64-linux-gnu/libusbmuxd-2.0.so.6 #2 0x7fac6037ce60 in ?? () from /lib/x86_64-linux-gnu/libusbmuxd-2.0.so.6 #3 0x7fac622a7fd4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #4 0x7fac6232866c in ?? () from /lib/x86_64-linux-gnu/libc.so.6 Thread 8 (Thread 0x7fac3e98c6c0 (LWP 493231) "QQuickPixmapRea"): #1 0x7fac611b59ae in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7fac611b5acc in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fac6270984e in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fac626b017b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fac624cab87 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fac643566d6 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #7 0x7fac624cbd43 in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fac622a7fd4 in ?? () from /lib/x86_64-linux-gnu/libc.so.6 #9 0x7fac6232866c in ?? () from /lib/x86_64-linux-gnu/libc.so.6 Thread 7 (Thread 0x7fac3f3ce6c0 (LWP 493230) "QSGRenderThread"): #1 0x7fac622a73f8 in pthread_cond_wait () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x7fac624d1a2b in QWaitCondition::wait(QMutex*, QDe
[kalendar] [Bug 467213] New: Crashed when editing event
https://bugs.kde.org/show_bug.cgi?id=467213 Bug ID: 467213 Summary: Crashed when editing event Classification: Applications Product: kalendar Version: 22.12.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: claudio.cam...@kde.org Reporter: ty.brown1...@gmail.com CC: c...@carlschwan.eu Target Milestone: --- Application: kalendar (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.15-200.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 37 (KDE Plasma) DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: I was editing the name of the event and then when done, I hit the 'enter' button and the application crashed The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Kalendar (kalendar), signal: Segmentation fault [KCrash Handler] #4 0x5608e8e4f413 in IncidenceOccurrenceModel::slotSourceDataChanged(QModelIndex const&, QModelIndex const&) () #5 0x7fe94eed0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #6 0x7fe94ee4dcd0 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #7 0x7fe94ee7f778 in QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #8 0x7fe94eed101f in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #9 0x7fe94ee4dcd0 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #10 0x7fe94ee7f778 in QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #11 0x7fe94eed101f in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #12 0x7fe94ee4dcd0 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #13 0x7fe94ee7f778 in QSortFilterProxyModelPrivate::_q_sourceDataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #14 0x7fe94eed101f in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #15 0x7fe94ee4dcd0 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #16 0x7fe9511c6a2a in KSelectionProxyModelPrivate::sourceDataChanged(QModelIndex const&, QModelIndex const&) () from /lib64/libKF5ItemModels.so.5 #17 0x7fe94eed0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #18 0x7fe94ee4dcd0 in QAbstractItemModel::dataChanged(QModelIndex const&, QModelIndex const&, QVector const&) () from /lib64/libQt5Core.so.5 #19 0x7fe9515034ab in Akonadi::EntityTreeModelPrivate::dataChanged(QModelIndex const&, QModelIndex const&) () from /lib64/libKF5AkonadiCore.so.5 #20 0x7fe95150ca82 in Akonadi::EntityTreeModelPrivate::monitoredItemChanged(Akonadi::Item const&, QSet const&) () from /lib64/libKF5AkonadiCore.so.5 #21 0x7fe94eed101f in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #22 0x7fe9514848bb in Akonadi::Monitor::itemChanged(Akonadi::Item const&, QSet const&) () from /lib64/libKF5AkonadiCore.so.5 #23 0x7fe95149b526 in Akonadi::MonitorPrivate::emitItemsNotification(Akonadi::Protocol::ItemChangeNotification const&, QVector const&, Akonadi::Collection const&, Akonadi::Collection const&) () from /lib64/libKF5AkonadiCore.so.5 #24 0x7fe9514938ca in Akonadi::MonitorPrivate::emitNotification(QSharedPointer const&) () from /lib64/libKF5AkonadiCore.so.5 #25 0x7fe951496f6c in Akonadi::MonitorPrivate::dispatchNotifications() () from /lib64/libKF5AkonadiCore.so.5 #26 0x7fe951492395 in Akonadi::MonitorPrivate::slotNotify(QSharedPointer const&) () from /lib64/libKF5AkonadiCore.so.5 #27 0x7fe95148f01e in Akonadi::MonitorPrivate::handleCommands() () from /lib64/libKF5AkonadiCore.so.5 #28 0x7fe94eec8134 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #29 0x7fe94fbaed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #30 0x7fe94ee9d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #31 0x7fe94eea0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #32 0x7fe94b07 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #33 0x7fe94cc63c7f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #34 0x7fe94ccba118 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #35 0
[Plasma Bigscreen] [Bug 463325] New: plasma-remotecontrollers crash, because it try to register listener for wayland when running X11
https://bugs.kde.org/show_bug.cgi?id=463325 Bug ID: 463325 Summary: plasma-remotecontrollers crash, because it try to register listener for wayland when running X11 Classification: Plasma Product: Plasma Bigscreen Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Remote Controllers Assignee: ai...@outlook.com Reporter: ty...@blackcentipede.com CC: plasma-b...@kde.org Target Milestone: --- Application: plasma-remotecontrollers (plasma-remotecontrollers), signal: Segmentation fault [KCrash Handler] #4 0x7ff74f0b38f2 in QtWaylandClient::QWaylandDisplay::addRegistryListener(void (*)(void*, wl_registry*, unsigned int, QString const&, unsigned int), void*) () from /usr/lib/libQt5WaylandClient.so.5 #5 0x7ff74f0d16b0 in QWaylandClientExtension::addRegistryListener() () from /usr/lib/libQt5WaylandClient.so.5 #6 0x7ff74e29c56e in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const () from /usr/lib/libQt5Core.so.5 #7 0x7ff74e29cf60 in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () from /usr/lib/libQt5Core.so.5 #8 0x55697b0a3c46 in ?? () #9 0x55697b0a540f in ?? () STEPS TO REPRODUCE 1. Install "plasma-bigscreen" package on ArchLinux 2. Login from SDDM for X11 Plasma 3. See plasma-remotecontrollers crash at login/start up. OBSERVED RESULT Plasma-remotecontrollers crash error dialog appears, because it attempts to register listener for Wayland server when Wayland is not running on X11 Plasma Shell. EXPECTED RESULT Should have no crash dialog appearing, if anything, it should terminates itself if wayland server is not detected. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.0.12-arch1-1 / 5.26.4 KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428618] Display configuration lists unsupported refreshrate
https://bugs.kde.org/show_bug.cgi?id=428618 Tyler changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458341] KWallet/SecretService: Support "plain" algorithm for DBus communications
https://bugs.kde.org/show_bug.cgi?id=458341 --- Comment #4 from Tyler Pate --- This change was either intentional or a regression. After upgrading KWallet today, I was locked out of my company VPN due to the plain algorithm being used in wallet communications between the VPN frontend and the keyring. The upgrade today was from KWallet 5.96.0 to 5.98.0. The plain algorithm support worked for versions 5.96 and lower. Therefore, a change to restrict this algorithm must have been introduced in 5.97. Can we not revert this change? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwallet] [Bug 458341] KWallet/SecretService: Support "plain" algorithm for DBus communications
https://bugs.kde.org/show_bug.cgi?id=458341 Tyler Pate changed: What|Removed |Added CC||tyler.graham.p...@gmail.com --- Comment #3 from Tyler Pate --- This change was either intentional or a regression. After upgrading KWallet today, I was locked out of my company VPN due to the plain algorithm being used in wallet communications between the VPN frontend and the keyring. The upgrade today was from KWallet 5.96.0 to 5.98.0. The plain algorithm support worked for versions 5.96 and lower. Therefore, a change to restrict this algorithm must have been introduced in 5.97. Can we not revert this change? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427861] Sometimes desktop loses its settings (wallpaper, widgets, icons settings) after re-login
https://bugs.kde.org/show_bug.cgi?id=427861 Tyler Pierce changed: What|Removed |Added CC||tyl...@praxisnine.com --- Comment #117 from Tyler Pierce --- Have been experiencing (I think) this same bug every re-boot since receiving pinephone pro completely updated I think: KDE Plasma Version: 5.25.5 KDE Framework Version: 5.98.0 QT Version: 5.15.6 Kernel Version: 5.19.11-1-MANJARO-ARM The behavior is sometimes after returning from a locked screen all icons have moved to the upper left of the desktop over top of each other and sometimes widgets resize slightly. But the main thing is on every re-boot it resets to the original factory desktop wallpaper/icons/widgets(none). Happy to add any info that may help investigation -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 451168] New: Context menus show up on the wrong monitor, or not at all.
https://bugs.kde.org/show_bug.cgi?id=451168 Bug ID: 451168 Summary: Context menus show up on the wrong monitor, or not at all. Product: kdenlive Version: 21.12.3 Platform: Flatpak OS: Linux Status: REPORTED Severity: major Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: tpoke.ferr...@gmail.com Target Milestone: --- Created attachment 147302 --> https://bugs.kde.org/attachment.cgi?id=147302&action=edit A video showing the issue. 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 *** STEPS TO REPRODUCE 1. Install Kdenlive on Fedora through flatpak 2. Connect multiple monitors to the computer 3. Use the menus on the toolbar OBSERVED RESULT The menus show up at the bottom of a different monitor or sometimes not at all. EXPECTED RESULT The menus show up, right below the toolbar SOFTWARE/OS VERSIONS Fedora Linux 36 (Workstation Edition Prerelease) ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448479] kwallet-pam no longer works on Wayland
https://bugs.kde.org/show_bug.cgi?id=448479 Tyler Gordon changed: What|Removed |Added CC||tgordon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 446539] New: right-click open terminal here in Dolphin crashes Dolphin
https://bugs.kde.org/show_bug.cgi?id=446539 Bug ID: 446539 Summary: right-click open terminal here in Dolphin crashes Dolphin Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: cipher...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 144247 --> https://bugs.kde.org/attachment.cgi?id=144247&action=edit Krash file from export. 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 *** STEPS TO REPRODUCE 1. Open Dolphin 2. Right click 3. Select open terminal here OBSERVED RESULT Crash EXPECTED RESULT terminal opening in current directory SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed (available in About System) KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION check kcrash file -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 389191] xwayland auto-upscaling causes pixelation and should be optional
https://bugs.kde.org/show_bug.cgi?id=389191 Tyler Gordon changed: What|Removed |Added CC||tgordon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436442] [systemd startup] kwallet fails to open at login most of the time
https://bugs.kde.org/show_bug.cgi?id=436442 Tyler Gordon changed: What|Removed |Added CC||tgordon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 443751] New: When pushing "Rescan" the number of GB already scanned doesn't reset to 0.
https://bugs.kde.org/show_bug.cgi?id=443751 Bug ID: 443751 Summary: When pushing "Rescan" the number of GB already scanned doesn't reset to 0. Product: filelight Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: martin.sandsm...@kde.org Reporter: mclemore...@gmail.com Target Milestone: --- Created attachment 142449 --> https://bugs.kde.org/attachment.cgi?id=142449&action=edit Video shows me rescanning the drive and the vyte count not reseting. SUMMARY When you scan a drive with filelight, you have the option to rescan at the top. If you push rescan, it shows the progress in the middle. The progress should reset to 0 everytime you rescan, but instead it keeps building up more and more. I am extremely aware of how poorly I'm describing this, so I've attached a video. STEPS TO REPRODUCE 1. Open filelight 2. Scan your drive and wait for it to finish 3. Click rescan at the top OBSERVED RESULT The total number of bytes scanned keeps increasing with each rescan EXPECTED RESULT The total number of bytes scanned should reset to 0 each time you rescan SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.20.5 KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 443668] New: Deleting a file of any size pins a cpu core
https://bugs.kde.org/show_bug.cgi?id=443668 Bug ID: 443668 Summary: Deleting a file of any size pins a cpu core Product: frameworks-kio Version: 5.78.0 Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Trash Assignee: fa...@kde.org Reporter: mclemore...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Deleting a file of any size will have the process "trash.so" STEPS TO REPRODUCE 1. Open ksysguard or top to view active processes and cpu ussage 2. Delete a file from within dolphin, preferably a small file for better demonstration 3. A Trash.so process will be made, and will pin one core on your machine 3. The takes at least 10 seconds (often times longer) to delete the file, regardless of actual size OBSERVED RESULT Item takes a long time to be deleted and uses a lot of system resources EXPECTED RESULT Should be similar to deleting a file by using 'rm'. Should be relatively instant and use few system resources. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441874] Custom Palettes are not loaded unless Krita is ran as administrator
https://bugs.kde.org/show_bug.cgi?id=441874 --- Comment #2 from Tyler Breau --- (In reply to tomtomtomreportingin from comment #1) > See https://bugs.kde.org/show_bug.cgi?id=440812 > > Does upgrading to 4.4.8 resolve your issue? Ah it does seem to resolve the issue. My bad. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 441874] New: Custom Palettes are not loaded unless Krita is ran as administrator
https://bugs.kde.org/show_bug.cgi?id=441874
Bug ID: 441874
Summary: Custom Palettes are not loaded unless Krita is ran as
administrator
Product: krita
Version: 4.4.5
Platform: Microsoft Windows
OS: Microsoft Windows
Status: REPORTED
Severity: minor
Priority: NOR
Component: * Unknown
Assignee: krita-bugs-n...@kde.org
Reporter: tylerbr...@hotmail.com
Target Milestone: ---
SUMMARY
STEPS TO REPRODUCE
1. Open without administrator permission krita document
2. Create a custom palette and check "Save Palette in the Current Document"
3. Open krita document without administrator permission
4. See custom palette is missing from your available palettes
5. Close krita
6. Open krita with administrator permission ("Run as Administrator")
7. Open your krita document
8. See your custom palette is in the available palette options
OBSERVED RESULT
Custom Palettes that are saved in the document disappear after closing and
re-opening the krita document, unless krita was opened with "Run as
Administrator".
EXPECTED RESULT
When Krita opens the document, it should be able to open palettes that were
saved in the document without administrator permissions.
SOFTWARE/OS VERSIONS
Windows: 10.0.19043 Build 19043
macOS:
Linux/KDE Plasma:
(available in About System)
KDE Plasma Version:
KDE Frameworks Version:
Qt Version: 5.12.9
ADDITIONAL INFORMATION
I didn't see anything regarding KDE Plasma or KDE Frameworks versions in Help
-> Show system information for bug reports.
If I am looking in the wrong place please notify me and I get the information
required.
A temporary work around for this issue is to notify users in the UI that custom
palettes saved in the document will not load unless krita is opened with the
"Run as Administrator" option.
This wouldn't really look pretty and is not really a solution but at least
users would be informed.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 439915] No feedback when dragging app from menu to panel when using touch
https://bugs.kde.org/show_bug.cgi?id=439915 Tyler Gordon changed: What|Removed |Added CC||tgordon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439917] Sometimes unable to rearrange pinned apps via touch
https://bugs.kde.org/show_bug.cgi?id=439917 Tyler Gordon changed: What|Removed |Added CC||tgordon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 440569] Virtual keyboard appears whenever an input field is activated for any reason even when a physical keyboard is attached
https://bugs.kde.org/show_bug.cgi?id=440569 Tyler Gordon changed: What|Removed |Added CC||tgordon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kdeclarative] [Bug 439920] DragArea requires press-and-hold with a touchscreen, which is unintuitive and undiscoverable
https://bugs.kde.org/show_bug.cgi?id=439920 Tyler Gordon changed: What|Removed |Added CC||tgordon...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 440624] Discover crashes when trying to run updates or install new software.
https://bugs.kde.org/show_bug.cgi?id=440624 --- Comment #2 from Tyler O'Connor --- Thank you. Sorry for that I am new to trying plasma on Debian. Tyler O’Connor Sent from ProtonMail for iOS On Thu, Aug 5, 2021 at 8:34 AM, Nate Graham wrote: > https://bugs.kde.org/show_bug.cgi?id=440624 > > Nate Graham changed: > > What |Removed |Added > > CC| |n...@kde.org > Severity|normal |crash > Status|REPORTED |RESOLVED > Resolution|--- |UNMAINTAINED > > --- Comment #1 from Nate Graham --- > Version 5.14.5 is almost three years old and is unsupported; please upgrade. > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[Plasma Workspace Wallpapers] [Bug 440625] New: Plasma Desktop loads black screen on login
https://bugs.kde.org/show_bug.cgi?id=440625 Bug ID: 440625 Summary: Plasma Desktop loads black screen on login Product: Plasma Workspace Wallpapers Version: 5.14.5 Platform: Debian stable OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: flip360...@protonmail.com Target Milestone: --- Created attachment 140534 --> https://bugs.kde.org/attachment.cgi?id=140534&action=edit Screen shot of black screen SUMMARY After installing Plasma-Desktop/Workspace on Debian. If I login to a Plasma season I get a black screen. Alt+F2 lets me search and run apps. Discover also crashes when using it which I filed a separate bug for. STEPS TO REPRODUCE 1. Install Plasma Desktop 2. Login to Plasma Desktop season 3. OBSERVED RESULT show logo splash screen, then loads a black screen. EXPECTED RESULT Plasma Desktop to load SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian GNU/Linux 10 (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION Sorry if I put this in the wrong area. I could not find Plasma Desktop or Workspace as an option to file the bug. Thank you. Operating System: Debian GNU/Linux 10 KDE Plasma Version: 5.14.5 Qt Version: 5.11.3 KDE Frameworks Version: 5.54.0 Kernel Version: 4.19.0-17-amd64 OS Type: 64-bit Processors: 16 × Intel® Xeon® CPU E5530 @ 2.40GHz Memory: 23.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 440624] New: Discover crashes when trying to run updates or install new software.
https://bugs.kde.org/show_bug.cgi?id=440624 Bug ID: 440624 Summary: Discover crashes when trying to run updates or install new software. Product: Discover Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: flip360...@protonmail.com CC: aleix...@kde.org Target Milestone: --- Created attachment 140533 --> https://bugs.kde.org/attachment.cgi?id=140533&action=edit crash report SUMMARY STEPS TO REPRODUCE 1. Open discover 2. Try to update or install some apps 3. OBSERVED RESULT Discover Crashes EXPECTED RESULT Being able to use the Discover software manager SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian GNU/Linux 10 (available in About System) KDE Plasma Version: 5.14.5 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.3 ADDITIONAL INFORMATION Operating System: Debian GNU/Linux 10 KDE Plasma Version: 5.14.5 Qt Version: 5.11.3 KDE Frameworks Version: 5.54.0 Kernel Version: 4.19.0-17-amd64 OS Type: 64-bit Processors: 16 × Intel® Xeon® CPU E5530 @ 2.40GHz Memory: 23.5 GiB of RAM -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439463] colors from unrelated document transferred onto current one, can't delete without starting a new blank document
https://bugs.kde.org/show_bug.cgi?id=439463 Tyler Bequeaith changed: What|Removed |Added Resolution|NOT A BUG |FIXED -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439463] colors from unrelated document transferred onto current one, can't delete without starting a new blank document
https://bugs.kde.org/show_bug.cgi?id=439463 --- Comment #2 from Tyler Bequeaith --- (In reply to Alvin Wong from comment #1) > That is probably a reference image. Try switching to the "Reference Image" > tool and remove it from there. OMG it worked. For some reason it is creating unwanted reference. I see that there is a shortcut (Ctl+Shift+R) for Paste as Reference Image, but I had only pressed Ctrl+C and Ctrl+V. Though I don't know why it would copy a selection of color from one document to the other without my knowledge. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439463] New: colors from unrelated document transferred onto current one, can't delete without starting a new blank document
https://bugs.kde.org/show_bug.cgi?id=439463 Bug ID: 439463 Summary: colors from unrelated document transferred onto current one, can't delete without starting a new blank document Product: krita Version: 4.4.5 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: major Priority: NOR Component: * Unknown Assignee: krita-bugs-n...@kde.org Reporter: manonfire2...@gmail.com Target Milestone: --- Created attachment 139837 --> https://bugs.kde.org/attachment.cgi?id=139837&action=edit This is the line group that I copied and pasted SUMMARY When working on an image, one group of lines I had selected to copy and paste appeared at the top left of my canvas. It wasn't on a layer and closing the program did not fix it ether. Then as I was looking back and forth between two documents all of one specific color (orange) was transferred from one document to the other, having the same ghostly properties as the lines I had copied earlier. It didn't exist on any layer and I couldn't cover it or move it, as if imprinted onto my screen but covered all the layers. This bug effectively ruined my piece and I had to copy and paste all my layers onto a new document. STEPS TO REPRODUCE 1. I am not sure exactly how it happens but it seems that multiple instances of the image on screen are created and the one that shouldn't exist is placed in the top left corner. 2. 3. OBSERVED RESULT An intangible duplicate of ether a segment of lines or all of one color on screen becoming locked on top of the canvas. EXPECTED RESULT An absence of freaky ghost copies ruining my canvas. SOFTWARE/OS VERSIONS Windows: 10 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION For the line segments I had copied and pasted I was luckily able to shrink the canvas to below where the lines were, but the lines did not disappear like any other lines or color that exceed the canvas. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428618] New: Display configuration lists unsupported refreshrate
https://bugs.kde.org/show_bug.cgi?id=428618 Bug ID: 428618 Summary: Display configuration lists unsupported refreshrate Product: systemsettings Version: 5.17.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: kcm_kscreen Assignee: kscreen-bugs-n...@kde.org Reporter: mclemore...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 132971 --> https://bugs.kde.org/attachment.cgi?id=132971&action=edit Shows a side by side of what display configuration has listed and the output of xrandr. (xrandr is correct) SUMMARY The listed refresh rate in display configuration is not actually supported by my screen. STEPS TO REPRODUCE 1. Open display configuration 2. Open the drop down menu for refresh rate OBSERVED RESULT The listed refresh rate differs from the actual refresh rate and other sources (like xrandr) EXPECTED RESULT Display configuration should list the correct refresh rates. SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.17.5 KDE Plasma Version: 5.17.5 KDE Frameworks Version: 5.74.0-2 Qt Version: 5.14.2-3 ADDITIONAL INFORMATION Laptop lenovo T580 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 427576] Update the kde-neon Snap extension to work with core20
https://bugs.kde.org/show_bug.cgi?id=427576 --- Comment #1 from Tyler Compton --- I've moved this bug to the Neon product, which seems more likely to be the right place. -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 427576] Update the kde-neon Snap extension to work with core20
https://bugs.kde.org/show_bug.cgi?id=427576 Tyler Compton changed: What|Removed |Added Product|Qt/KDE Flatpak Runtime |neon Component|general |Snaps Assignee|aleix...@kde.org|neon-b...@kde.org CC||neon-b...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 427576] New: Update the kde-neon Snap extension to work with core20
https://bugs.kde.org/show_bug.cgi?id=427576 Bug ID: 427576 Summary: Update the kde-neon Snap extension to work with core20 Product: Qt/KDE Flatpak Runtime Version: unspecified Platform: Snap OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: aleix...@kde.org Reporter: xavi...@gmail.com Target Milestone: --- SUMMARY Currently, the kde-neon Snap extension only supports core18. It would be great to get a core20 version, so Qt applications using Snap can run from that base. I'm certain this is the wrong product to submit this bug to, but I couldn't find any products related to KDE's general Snap support. Sorry about that. Please move this to wherever it needs to go, or I'll be happy to file a new issue if someone points me in the right direction. STEPS TO REPRODUCE 1. Create a snapcraft.yaml whose `base` field is `core20` and lists `kde-neon` in the `extensions` field. 2. Run `snapcraft` 3. Observe the following error: Failed to load extension 'kde-neon': this extension does not support the 'core20' base. Either use a different extension, or use a base supported by this extension. OBSERVED RESULT Snapcraft reports that the kde-neon extension doesn't support the `core20` base. EXPECTED RESULT Snapcraft finds a version of the kde-neon extension that supports this base and the build finishes. SOFTWARE/OS VERSIONS N/A ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425085] Export to flickr dialog only allows a single file to be selected
https://bugs.kde.org/show_bug.cgi?id=425085 Tyler Spaeth changed: What|Removed |Added Resolution|FIXED |NOT A BUG Version|unspecified |7.0.0 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425085] Export to flickr dialog only allows a single file to be selected
https://bugs.kde.org/show_bug.cgi?id=425085 Tyler Spaeth changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Tyler Spaeth --- Ah, sorry. I looked in the docs and google searched, but apparently I'm bad at it. Thank you so much! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 425085] New: Export to flickr dialog only allows a single file to be selected
https://bugs.kde.org/show_bug.cgi?id=425085 Bug ID: 425085 Summary: Export to flickr dialog only allows a single file to be selected Product: digikam Version: unspecified Platform: macOS (DMG) OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Plugin-WebService-Flickr Assignee: digikam-bugs-n...@kde.org Reporter: ty...@linkless.org Target Milestone: --- SUMMARY When using the Export > Export to Flickr... menu item, I am presented with a dialog box that seems to require me to select a file on the file system. I am unable to select a directory and can only select a single file. Select all and shift and cmd clicking don't select multiple files. This is true if I use the + button or the file folder icon button. I'd like to be able to sync and combination of selected tags, but I don't see any option for that. All export options (SmugMug etc) seem to present the same dialog, though with different login options. This might be a wish list item, but I'd also like to not have to select anything off the filesystem, and use the Digikam standard interface to export any items in the current filter or by tag. Albums are insufficient for my needs. I love Digikam, but this is probably a deal breaker unless I roll some code to sync with Photos (which I might :-)). STEPS TO REPRODUCE 1. Click the Export > Export to Flickr... menu item. 2. Select an account. 3. Click any button that prompts for files (+ or the file folder icon at the bottom). 4. Try to select a directory or more than one image. OBSERVED RESULT Only a single image is selectable. EXPECTED RESULT Any number of images should be able to opened/selected. SOFTWARE/OS VERSIONS Windows: macOS: 10.15.5 (19F101) Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Digikam 7.0 Build date: Jul 16 2020 (target: Debug) Rev.: 934afab2a5b29917004215cfa02e613082881ba1 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 425010] New: Apple Pencil is not in sync with the mouse when drawing on canvas
https://bugs.kde.org/show_bug.cgi?id=425010 Bug ID: 425010 Summary: Apple Pencil is not in sync with the mouse when drawing on canvas Product: krita Version: 4.3.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: noverthequa...@icloud.com Target Milestone: --- SUMMARY I am using an iPad with an Apple Pencil. I utilize sidecar with my Mac mini, and use my iPad as a graphics tablet. when I was using Arita and safari at the same time (displays are not mirrored), I somehow saw that the Apple Pencil is off sync with the canvas. if I try to dray in the center nothing happens; but if I try to draw downward, the line that the pencil was supposed to create ends up on the top of the canvas. I've seen this happen before but this is the first time I'm reporting this as a bug. SOFTWARE/OS VERSIONS Windows: N/A macOS: 10.15.6 Linux/KDE Plasma: N/A (available in About System) KDE Plasma Version: N/A KDE Frameworks Version: N/A Qt Version: N/A ADDITIONAL INFORMATION I am running on an iPad 7th Generation running iPadOS 13.6 with Apple Pencil and sidecar. it is not jailbroken. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #25 from Tyler Brown --- So far I run into this issue when I pull from git and run the install script on Kubuntu 20.04 and Fedora 32 KDE. For the hell of it I decided to do the same on my openSUSE Tumbleweed desktop and it works just fine. Is there something out of date on Kubuntu 20.04 or Fedora 32 that would be causing any build issues? I've got all the dependencies listed on Phabricator so I it's not throwing any complaints that I'm missing anything that the documentation requires of me. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #24 from Tyler Brown --- Created attachment 128591 --> https://bugs.kde.org/attachment.cgi?id=128591&action=edit Reproduced from a clean layout. Reproducing the issue from a clean layout. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #22 from Tyler Brown --- Some more testing around and I found that playing with the min/max length of the panel will impact whether or not the Latte Tasks disappears. 1. If the min and max value match then it disappears. 2. If I keep opening applications it will actually proceed to ignore the max and just keep growing the panel instead of shrinking. 3. If the min is set to 100% or it's set to panel mode using justified then Latte Tasks disappears. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #20 from Tyler Brown --- (In reply to Michail Vourlakos from comment #18) > try to remove everything in : /usr/lib64/qt5/qml/org/kde/latte/ > and reinstall Latte, does it still occur? Purged that directory and reinstalled using the install script, did not work, issue still occurring on both Fedora 32 and Kubuntu 20.04. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #17 from Tyler Brown --- Another update: Tried building from the script on Kubuntu 20.04, all required dev packages installed, same issue occurs when enabling scrolling. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #16 from Tyler Brown --- On my openSUSE Tumbleweed desktop where I'm running the latest git version from trmdi's OBS repo I'm not having this issue, in fact it's working perfectly. Information for package latte-dock: --- Repository : home:trmdi Name : latte-dock Version: 999.git.20200517.b264854a-465.1 Arch : x86_64 Vendor : obs://build.opensuse.org/home:trmdi Installed Size : 3.4 MiB Installed : Yes Status : up-to-date Source package : latte-dock-999.git.20200517.b264854a-465.1.src Summary: Task manager On both of my Fedora laptops I went through and made sure all the necessary devel packages were installed, and I'm not getting any warning that anything is missing when I'm running the install script. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #15 from Tyler Brown --- Created attachment 128569 --> https://bugs.kde.org/attachment.cgi?id=128569&action=edit Latte Scroll On -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #14 from Tyler Brown --- Created attachment 128568 --> https://bugs.kde.org/attachment.cgi?id=128568&action=edit LatteScrollOff -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #9 from Tyler Brown --- The issue still remains after removing those directories and reinstalling Latte Dock. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 401322] Unable to click the canvas rotation button in the pop-up palette when in Hidpi mode.
https://bugs.kde.org/show_bug.cgi?id=401322 Tyler changed: What|Removed |Added Ever confirmed|0 |1 Version|4.1.5 |4.2.9 Status|RESOLVED|REOPENED Resolution|FIXED |--- --- Comment #6 from Tyler --- I think something is broken with hidpi handling again. Running 4.2.9 here.There is definitely an offset with the cursor when using a stylus pen. Couldn't even click the top menu items like Settings, File, etc. with my pen. I have the "hidpi support" option checked in settings. If I uncheck that, the offset seems to go away. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #7 from Tyler Brown --- I clone it from here and run the install script: https://phabricator.kde.org/source/latte-dock/ -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #5 from Tyler Brown --- Created attachment 128559 --> https://bugs.kde.org/attachment.cgi?id=128559&action=edit Recording of tasks disappearing. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #4 from Tyler Brown --- I am able to reproduce this with a new default layout. I'm also not seeing anything weird when I toggle the setting when launching Latte Dock from the terminal with the debug flag. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 --- Comment #3 from Tyler Brown --- Created attachment 128558 --> https://bugs.kde.org/attachment.cgi?id=128558&action=edit Layout File My current layout file as if this moment. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] New: Widget disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 Bug ID: 421697 Summary: Widget disappears when scrolling is enabled. Product: lattedock Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: ty...@condoulo.com Target Milestone: --- Created attachment 128557 --> https://bugs.kde.org/attachment.cgi?id=128557&action=edit Desktop with application open not showing in Tasks. SUMMARY STEPS TO REPRODUCE 1. Go into the Tasks Tab of Settings 2. Enable Scrolling 3. OBSERVED RESULT Tasks disappear EXPECTED RESULT Scrolling should be enabled SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Fedora 32 KDE / 5.6.11-300.fc32.x86_64 (available in About System) KDE Plasma Version: Plasma 5.18.5 KDE Frameworks Version: 5.68.0 Qt Version: 5.13.2 Latte Dock: Latest Git build as of 2020-05-17 16:29 CDT. ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421697] Tasks disappears when scrolling is enabled.
https://bugs.kde.org/show_bug.cgi?id=421697 Tyler Brown changed: What|Removed |Added Summary|Widget disappears when |Tasks disappears when |scrolling is enabled. |scrolling is enabled. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421386] crashes when editing a panel
https://bugs.kde.org/show_bug.cgi?id=421386 --- Comment #12 from Tyler Brown --- I pulled down the latest Unity indicator from Git and that resolved the issues on my end. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421386] crashes when editing a panel
https://bugs.kde.org/show_bug.cgi?id=421386 --- Comment #4 from Tyler Brown --- (In reply to Michail Vourlakos from comment #3) > (In reply to Tyler Brown from comment #2) > > I get this issue when I try to edit a panel that is either using a 3rd party > > Indicator theme or whenever I try to set a 3rd party Indicator theme, such > > as the Unity on W7 indicators. Latest version pulled from Phabricator within > > the last couple of hours. > > you mean that it crashes only when you are trying to choose a 3rd party > indicator? Both. It'll crash when I try to choose one, but it also crashes when I open "Edit Panel" on a panel that already has a 3rd party indicator set. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421386] crashes when editing a panel
https://bugs.kde.org/show_bug.cgi?id=421386 Tyler Brown changed: What|Removed |Added CC||ty...@condoulo.com --- Comment #2 from Tyler Brown --- I get this issue when I try to edit a panel that is either using a 3rd party Indicator theme or whenever I try to set a 3rd party Indicator theme, such as the Unity on W7 indicators. Latest version pulled from Phabricator within the last couple of hours. -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 419445] New: Ksysguard System Load graph goes up to 102%
https://bugs.kde.org/show_bug.cgi?id=419445 Bug ID: 419445 Summary: Ksysguard System Load graph goes up to 102% Product: ksysguard Version: 5.17.5 Platform: Debian testing OS: Linux Status: REPORTED Severity: task Priority: NOR Component: ksysguard Assignee: ksysguard-b...@kde.org Reporter: mclemore...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 127126 --> https://bugs.kde.org/attachment.cgi?id=127126&action=edit The picture shows the graph with a max value of 102% SUMMARY The Ksysguard System Load window will sometimes have the maximum value on the left hand side of te graph be 102%, when 100% is clearly the highest the graph can ever be. STEPS TO REPRODUCE 1. Have Ksysguard be in windowed mode 2. Vertically resize the window so the scale changes. OBSERVED RESULT At certain sizes the scale will be between 0 and 102 instead of 0 and 100 EXPECTED RESULT The graph should always be between 0 and 100 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.
[ksysguard] [Bug 419445] Ksysguard System Load graph goes up to 102%
https://bugs.kde.org/show_bug.cgi?id=419445 Tyler changed: What|Removed |Added CC||mclemore...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417587] Font Setting cannot be saved and font size are defaulted to 6 without any ability to change it.
https://bugs.kde.org/show_bug.cgi?id=417587 --- Comment #1 from Tyler --- Someone just pointed out that a bug report is already made for this: 416358 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 416358] kcm_fonts: Cannot apply changes (button remains inactive)
https://bugs.kde.org/show_bug.cgi?id=416358 Tyler changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=417587 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417587] Font Setting cannot be saved and font size are defaulted to 6 without any ability to change it.
https://bugs.kde.org/show_bug.cgi?id=417587 Tyler changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=416358 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 417587] New: Font Setting cannot be saved and font size are defaulted to 6 without any ability to change it.
https://bugs.kde.org/show_bug.cgi?id=417587 Bug ID: 417587 Summary: Font Setting cannot be saved and font size are defaulted to 6 without any ability to change it. Product: systemsettings Version: 5.18.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: kcm_fonts Assignee: plasma-b...@kde.org Reporter: ty...@blackcentipede.com Target Milestone: --- SUMMARY The font size on KDE Plasma desktop is shrunk to font size 6 which is barely readable and when entering into Plasma Desktop Setting for Font management to adjust both the force DPI and font size for all fonts, it does not save the settings. The apply button is greyed out when font settings are changed. When re-opening the setting, the settings are back to the original state without any of my modification to the settings. I've also tried restarting the machine upon modifying the setting. I am essentially stuck on font size 6 without any way to change it. STEPS TO REPRODUCE 1. Open Plasma Desktop Setting 2. Go to Font Management in Setting 3. Adjust Font Size or Forced DPI Setting OBSERVED RESULT Apply button greyed out and nothing in the setting is saved. EXPECTED RESULT Apply button should not be greyed out and should save the settings upon clicking on apply and the effect should be seen after restarting Plasma Desktop. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux (Latest today) 5.18-1 plasma-meta package KDE Plasma Version: 5.18 KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION Prior version 5.17.90 does not have this regression. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414692] New: Line Styles do not save.
https://bugs.kde.org/show_bug.cgi?id=414692 Bug ID: 414692 Summary: Line Styles do not save. Product: krita Version: unspecified Platform: MS Windows OS: MS Windows Status: REPORTED Severity: normal Priority: NOR Component: Tools/Vector Assignee: krita-bugs-n...@kde.org Reporter: tylerbr...@hotmail.com Target Milestone: --- Created attachment 124212 --> https://bugs.kde.org/attachment.cgi?id=124212&action=edit My project where I see the bug SUMMARY I'm trying to use Tool Options -> Line Styles to disable the border around some vectors. I would make my changes, save the project, and then close. When re-opening the project the Line Styles would be set back to a solid line (from no line). I'm not sure how to create a new project re-producing this, so I'll provide my project. STEPS TO REPRODUCE Note: Some of the terminology will be referencing stuff in my project. 1. Select any number of tiles in the Tiles Area layer. 2. Set Line Style to no line in Tool Options. 3. Save the project. 4. Close the project. 5. Open the project. 6. See Line Styles have changed back to solid line. OBSERVED RESULT Line Styles do not save. EXPECTED RESULT Line Styles should save. SOFTWARE/OS VERSIONS Windows: 10 macOS: N/A Linux/KDE Plasma: (available in About System) KDE Plasma Version: N/A KDE Frameworks Version: LGPLv2.1+ Qt Version: GPLv2 + GPLv3 + LGPLv2.1 + LGPLv3 ADDITIONAL INFORMATION I just recently found out I could also simply disable the borders by clicking the square with an red X. From what I can tell, this options DOES save properly. It is NOT to be confused with setting the Line Style. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407978] Popup palette closes instantly with stylus
https://bugs.kde.org/show_bug.cgi?id=407978 --- Comment #20 from Tyler --- It seems that when I tick the checkbox which says "Use mouse events for right- and middle-clicks..." in Tablet settings, I'm not affected by this bug anymore. Strange... I don't have to do this with the Appimage version. My tablet is this one: https://www.wacom.com/en-in/products/pen-tablets/one-by-wacom#Specifications. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407978] Popup palette closes instantly with stylus
https://bugs.kde.org/show_bug.cgi?id=407978 --- Comment #18 from Tyler --- (In reply to Antonio Rojas from comment #17) > (In reply to Tyler from comment #16) > > (In reply to Boudewijn Rempt from comment #13) > > > there's another possibility, too, now that I think of it. The appimage > > > cannot load the KDE plasma Qt platform plugin that might be present on > > > your > > > systems, and that does stuff about single and double mouse clicks. If > > > you're > > > using plasma, does changing the single/doubleclick setting make a > > > difference? > > > > I'm running Gnome though. > > Gnome also has its own platform plugin. Try running it with > > XDG_CURRENT_DESKTOP="foo" krita No. That didn't help. Here is the output I got: Invalid profile : "/usr/share/color/icc/colord/Crayons.icc" "Crayon Colors" Invalid profile : "/usr/share/color/icc/colord/x11-colors.icc" "X11 Colors" QObject::startTimer: Timers cannot have negative intervals Traceback (most recent call last): File "", line 1, in ModuleNotFoundError: No module named 'sip' krita.scripting: "Traceback (most recent call last):" krita.scripting: " File \"/usr/lib/krita-python-libs/krita/__init__.py\", line 7, in " krita.scripting: "from .api import *" krita.scripting: " File \"/usr/lib/krita-python-libs/krita/api.py\", line 28, in " krita.scripting: "from PyKrita.krita import *" krita.scripting: "ModuleNotFoundError: No module named 'PyQt5'" krita.scripting: "Could not import krita" -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408331] Brush size display in toolbar not updated correctly
https://bugs.kde.org/show_bug.cgi?id=408331 --- Comment #2 from Tyler --- (In reply to vanyossi from comment #1) > Is there any preset in particular that does this more than other? > > On my setup I can't reproduce at all, size is always correct and on the same > number as popup palette. I think I always start with Airbrush. It appears to be happening only when Krita is started with Airbrush as last used brush. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407978] Popup palette closes instantly with stylus
https://bugs.kde.org/show_bug.cgi?id=407978 --- Comment #16 from Tyler --- (In reply to Boudewijn Rempt from comment #13) > there's another possibility, too, now that I think of it. The appimage > cannot load the KDE plasma Qt platform plugin that might be present on your > systems, and that does stuff about single and double mouse clicks. If you're > using plasma, does changing the single/doubleclick setting make a difference? I'm running Gnome though. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407978] Popup palette closes instantly with stylus
https://bugs.kde.org/show_bug.cgi?id=407978 --- Comment #12 from Tyler --- (In reply to Boudewijn Rempt from comment #11) > Okay. Do you know whether Arch adds any patches of their own to Qt? Not that I know of. @Antonio Rojas (He's in the cc list) is probably the right person to answer this. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407978] Popup palette closes instantly with stylus
https://bugs.kde.org/show_bug.cgi?id=407978 --- Comment #10 from Tyler --- (In reply to Boudewijn Rempt from comment #9) > But not with with the appimage, right? Yep. Appimage version is not affected by this bug. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407978] Popup palette closes instantly with stylus
https://bugs.kde.org/show_bug.cgi?id=407978 --- Comment #8 from Tyler --- (In reply to Boudewijn Rempt from comment #7) > And 4.2.1? That was rebased on Qt 5.12.3, too. Sorry. Typo: I'm having the issue withe both 4.2.0 and 4.2.1 (not 4.1.2). Tested with qt-base 5.12.3 in Arch repo, patched with the patches mentioned in my previous comment. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 407978] Popup palette closes instantly with stylus
https://bugs.kde.org/show_bug.cgi?id=407978 Tyler changed: What|Removed |Added CC||tftyler...@gmail.com --- Comment #6 from Tyler --- Having the same issue with 4.2.0 stable and 4.1.2. The appimage version works fine though. I'm on Arch Linux. I've tried rebuilding qt-base (which is 5.12.3 in Arch) with patches mentioned here: https://phabricator.kde.org/T10838: Namely: https://codereview.qt-project.org/#/c/252182/ https://codereview.qt-project.org/#/c/258193/ https://codereview.qt-project.org/#/c/255384/ https://codereview.qt-project.org/#/c/255382/ But didn't help. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 408331] New: Brush size display in toolbar not updated correctly
https://bugs.kde.org/show_bug.cgi?id=408331 Bug ID: 408331 Summary: Brush size display in toolbar not updated correctly Product: krita Version: 4.2.1 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: tftyler...@gmail.com Target Milestone: --- Created attachment 120594 --> https://bugs.kde.org/attachment.cgi?id=120594&action=edit screenshot SUMMARY Sometime when using shift+draw in canvas or [] to change brush size, the size display in the toolbar is not updated correctly according to the actual brush size. Size display in the popup palette is correct though. STEPS TO REPRODUCE 1. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406235] Dodge all windows causes dock to hide on empty desktop
https://bugs.kde.org/show_bug.cgi?id=406235 --- Comment #15 from Tyler Brown --- Created attachment 119261 --> https://bugs.kde.org/attachment.cgi?id=119261&action=edit Current layout file Current layout file -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406235] Dodge all windows causes dock to hide on empty desktop
https://bugs.kde.org/show_bug.cgi?id=406235 --- Comment #13 from Tyler Brown --- Created attachment 119260 --> https://bugs.kde.org/attachment.cgi?id=119260&action=edit Hotcorner settings Even with all hotcorner and touchscreen settings disabled the issue still occurs. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406235] Dodge all windows causes dock to hide on empty desktop
https://bugs.kde.org/show_bug.cgi?id=406235 --- Comment #12 from Tyler Brown --- Created attachment 119259 --> https://bugs.kde.org/attachment.cgi?id=119259&action=edit Touchscreen Settings -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406235] Dodge all windows causes dock to hide on empty desktop
https://bugs.kde.org/show_bug.cgi?id=406235 --- Comment #8 from Tyler Brown --- (In reply to Michail Vourlakos from comment #7) > If you disable all touch gestures from plasma system settings, is it fixed? I didn't have any of the touch gestures enabled in the plasma system settings. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406235] Dodge all windows causes dock to hide on empty desktop
https://bugs.kde.org/show_bug.cgi?id=406235 --- Comment #6 from Tyler Brown --- (In reply to Michail Vourlakos from comment #5) > 5. Changing from left to bottom edge, same problem? 5. The issue does not occur with a dock/panel on the bottom. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406235] Dodge all windows causes dock to hide on empty desktop
https://bugs.kde.org/show_bug.cgi?id=406235 --- Comment #4 from Tyler Brown --- Created attachment 119254 --> https://bugs.kde.org/attachment.cgi?id=119254&action=edit Envoutput 1&2: I pulled down the latest right before submitting this bug report and installed it with the install.sh script. 3. Attached. 4. Only a single display is attached. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406235] Dodge all windows causes dock to hide on empty desktop
https://bugs.kde.org/show_bug.cgi?id=406235 --- Comment #2 from Tyler Brown --- This issue does not occur with the Dodge Active Windows. It also does not occur with the Dodge Maxmized setting. It only occurs under Dodge All Windows. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406235] New: Dodge all windows causes dock to hide on empty desktop
https://bugs.kde.org/show_bug.cgi?id=406235 Bug ID: 406235 Summary: Dodge all windows causes dock to hide on empty desktop Product: lattedock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: ty...@condoulo.com Target Milestone: --- Created attachment 119250 --> https://bugs.kde.org/attachment.cgi?id=119250&action=edit Video showing the dock dodging the desktop SUMMARY STEPS TO REPRODUCE 1. Enable dodge all windows 2. Click anywhere on the desktop 3. OBSERVED RESULT Dock hides as if it is treating the plasmashell desktop as a window EXPECTED RESULT Dock should not hide as there is no proper window to dodge. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 18.10; Kernel 4.18.0-16-generic; (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406070] Unity Style Indicators now result in a white box
https://bugs.kde.org/show_bug.cgi?id=406070 --- Comment #3 from Tyler Brown --- 1. I am running the latest git version (Just pulled it in within the last hour). 2. It seems running that command to relaunch Latte-Dock has fixed the issue. Must've been a one off? Strange. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406070] Unity Style Indicators now result in a white box
https://bugs.kde.org/show_bug.cgi?id=406070 --- Comment #1 from Tyler Brown --- An additional note: This only impacts applications that are open and showing. This issue does not manifest with minimized applications. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 406070] New: Unity Style Indicators now result in a white box
https://bugs.kde.org/show_bug.cgi?id=406070 Bug ID: 406070 Summary: Unity Style Indicators now result in a white box Product: lattedock Version: git (master) Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: plasmoid Assignee: mvourla...@gmail.com Reporter: ty...@condoulo.com Target Milestone: --- Created attachment 119173 --> https://bugs.kde.org/attachment.cgi?id=119173&action=edit White boxes SUMMARY STEPS TO REPRODUCE 1. Enable Unity indicators 2. 3. OBSERVED RESULT Application icons are replaced with a white box EXPECTED RESULT Application icons should have the square Unity style indicator SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Kubuntu 18.10 (available in About System) KDE Plasma Version: 5.15.3 KDE Frameworks Version: 5.54.0 Qt Version: 5.11.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404668] Panel Goes Black With Window Touching
https://bugs.kde.org/show_bug.cgi?id=404668 --- Comment #6 from Tyler Brown --- Created attachment 118278 --> https://bugs.kde.org/attachment.cgi?id=118278&action=edit My Latte Layout Here is my Latte Layout File. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404668] Panel Goes Black With Window Touching
https://bugs.kde.org/show_bug.cgi?id=404668 --- Comment #3 from Tyler Brown --- Created attachment 118276 --> https://bugs.kde.org/attachment.cgi?id=118276&action=edit My Normal Panel This is what my top panel looks like normally with "Colors From Window" set to None. -- You are receiving this mail because: You are watching all bug changes.
[latte-dock] [Bug 404668] Panel Goes Black With Window Touching
https://bugs.kde.org/show_bug.cgi?id=404668 --- Comment #4 from Tyler Brown --- Created attachment 118277 --> https://bugs.kde.org/attachment.cgi?id=118277&action=edit Example Colors File Here is an example color scheme file, this is Adapta modified slightly to match the color scheme of Discord's window. Although this happens with any color scheme, including the regular Adapta. -- You are receiving this mail because: You are watching all bug changes.
