[plasmashell] [Bug 469016] Plasma panel visually (but not functionally) freezing on Wayland with Basic render loop and Non-Intel GPU when Task Manager previews are turned on
https://bugs.kde.org/show_bug.cgi?id=469016 --- Comment #98 from Monica --- Wanted to say that I tried running `kcmshell5 kcm_qtquicksettings` and tried setting the rendering back end to OpenGL (on a hunch) and setting the render loop to Threaded (as per what the general consensus is to fix it) to same result. That leads me to believe that either 1. The automatic settings for both of those just happened to be what I manually set it to by happenstance 2. The threaded renderer isn't exactly the solution that should be chased after Should 2 be the answer, it being the default option in Plasma 6 wouldn't resolve this issue. Since my prior issue was marked as a duplicate (issue #477946), I figured I'd share my findings here -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477946] New: Icon-Only Task Manager hangs under wayland
https://bugs.kde.org/show_bug.cgi?id=477946 Bug ID: 477946 Summary: Icon-Only Task Manager hangs under wayland Classification: Plasma Product: plasmashell Version: 5.90.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: wolfmurdure...@gmail.com CC: qydwhotm...@gmail.com Target Milestone: 1.0 SUMMARY While running under Wayland, the Icon-Only Task Manager appears to hang, as observed by the clock not progressing. Task Manager is still usable by clicking on icons of programs that are currently open, but the state (e.g., currently in foreground, background, minimized, whether it's opened or not) does not change. Rebooting the system temporarily fixes the issue and occurs in seemingly random situations and does not appear to be load related. STEPS TO REPRODUCE 1. Load Plasma 5 in Wayland 2. Wait OBSERVED RESULT Time freezes and program states are stuck as of when the task manager froze. EXPECTED RESULT The task manager runs reliably without freezing SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.27.9 (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION The issue appears to be unrelated to GPUs, as I have tried to troubleshoot this with a GTX 1080, RX 570 4GB, and an RTX 3060 12GB, with the Nvidia cards having the latest proprietary drivers at that time, and the RX 570 utilizing amdgpu. Issue has persisted from April 2023 to today (December 2nd, 2023) across Fedora Linux versions 37, 38, and 39. Worth noting that I have not tested it outside of Fedora Linux or with the regular task manager (not Icon-Only). Other details that might be worth noting: - AMD Ryzen 5 3600 (Stock) - ASUS ROG STRIX B450-F - 32 GB DDR4 @ 3600MHz - Disks: - 1x CT2000MX500SSD1 (Mounted as /home, ext4, LUKS encrypted) - 1x WD Blue (Mounted at /mnt/local-backup, ext4, usually left unmounted) - 1x Samsung SSD 970 EVO 250GB (p1 mounted at /boot/efi as vfat, p2 mounted at /boot as ext4, p3 mounted at / as btrfs) - 1x Samsung SSD 980 EVO 250GB (Windows drive, left unmounted) Additional logs, videos, and screenshots can be provided upon request -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467859] New: Copying large amount of data to webdav crashes Dolphin
https://bugs.kde.org/show_bug.cgi?id=467859 Bug ID: 467859 Summary: Copying large amount of data to webdav crashes Dolphin Classification: Applications Product: dolphin Version: 22.12.3 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: wolfmurdure...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.7-200.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: "Fedora release 37 (Thirty Seven)" DrKonqi: 5.27.3 [KCrashBackend] -- Information about the crash: While copying ~4.6 GiB of data to a Nextcloud server via WebDav, Dolphin eventually crashed and cancelled the copy. Of note, I was trying to open a .tar.gz file from the source directory (stored locally) with Ark, of which crashed at the same time as Dolphin. Additionally, the WebDav share kept disconnecting, prompting me to reconnect after each disconnect. Expected behavior: copy finishes Actual behavior: Multiple disconnects, crashing after copying 572 MiB of data. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f5d3452e49a in KJobWidgets::window(KJob*) () from /lib64/libKF5JobWidgets.so.5 #5 0x7f5d3464afaf in KIO::WidgetsAskUserActionHandler::askUserSkip(KJob*, QFlags, QString const&) () from /lib64/libKF5KIOWidgets.so.5 #6 0x7f5d343a56ba in KIO::CopyJobPrivate::slotResultErrorCopyingFiles(KJob*) () from /lib64/libKF5KIOCore.so.5 #7 0x7f5d326d0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #8 0x7f5d33be3449 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #9 0x7f5d33be8edb in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5 #10 0x7f5d326d0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #11 0x7f5d33be3449 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #12 0x7f5d33be8edb in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5 #13 0x7f5d326d0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #14 0x7f5d343c8c5a in KIO::SlaveInterface::error(int, QString const&) () from /lib64/libKF5KIOCore.so.5 #15 0x7f5d343d12f8 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #16 0x7f5d343c8a8a in KIO::SlaveInterface::dispatch() () from /lib64/libKF5KIOCore.so.5 #17 0x7f5d343cb2f1 in KIO::Slave::gotInput() () from /lib64/libKF5KIOCore.so.5 #18 0x7f5d326d0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #19 0x7f5d326c8134 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #20 0x7f5d333aed62 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #21 0x7f5d3269d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #22 0x7f5d326a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #23 0x7f5d326eeb07 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #24 0x7f5d30518c7f in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #25 0x7f5d3056f118 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #26 0x7f5d30515f00 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #27 0x7f5d326ee5fa in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #28 0x7f5d3269bf3a in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #29 0x7f5d326a4002 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #30 0x564376b50135 in main () [Inferior 1 (process 13491) detached] The reporter indicates this bug may be a duplicate of or related to bug 444679. Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 457420] New: Dolphin crashes upon accessing SMB shares
https://bugs.kde.org/show_bug.cgi?id=457420 Bug ID: 457420 Summary: Dolphin crashes upon accessing SMB shares Product: dolphin Version: 22.04.1 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: wolfmurdure...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.04.1) Qt Version: 5.15.3 Frameworks Version: 5.96.0 Operating System: Linux 5.18.10-200.fc36.x86_64 x86_64 Windowing System: X11 Distribution: "Fedora release 36 (Thirty Six)" DrKonqi: 5.25.2 [KCrashBackend] -- Information about the crash: Description: While trying to access an SMB share (either via IP or DNS), it immediately crashes dolphin, extremely consistent behavior Expected Results: After typing in `smb://hostname.local`, it presents the shares of device `hostname` Actual results: Crashes Dolphin The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f42531ba0f0 in KCoreDirListerCache::slotUpdateResult(KJob*) () from /lib64/libKF5KIOCore.so.5 #5 0x7f42517f3c36 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #6 0x7f425298cd29 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #7 0x7f425299234b in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5 #8 0x7f42517f3c36 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #9 0x7f4253162bc0 in KIO::SlaveInterface::dispatch(int, QByteArray const&) () from /lib64/libKF5KIOCore.so.5 #10 0x7f425315dfba in KIO::SlaveInterface::dispatch() () from /lib64/libKF5KIOCore.so.5 #11 0x7f4253160611 in KIO::Slave::gotInput() () from /lib64/libKF5KIOCore.so.5 #12 0x7f42517f3c36 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #13 0x7f42517ea694 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #14 0x7f4252357c82 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #15 0x7f42517c0658 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #16 0x7f42517c39b4 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #17 0x7f4251811807 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () from /lib64/libQt5Core.so.5 #18 0x7f424f410faf in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #19 0x7f424f4662c8 in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #20 0x7f424f40e940 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #21 0x7f42518112fa in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #22 0x7f42517bf0ba in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #23 0x7f42517c7162 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #24 0x561c6f6239e7 in main () [Inferior 1 (process 111446) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 455731] connecting to a smb-share
https://bugs.kde.org/show_bug.cgi?id=455731 Monica changed: What|Removed |Added Platform|Ubuntu Packages |Fedora RPMs CC||wolfmurdure...@gmail.com --- Comment #1 from Monica --- Description: While trying to access an SMB share (either via IP or DNS), it immediately crashes dolphin, extremely consistent behavior Expected Results: After typing in `smb://hostname.local`, it presents the shares of device `hostname` Actual results: Crashes Dolphin -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439136] New: version 4.4.5 is damaged and won't open on MacOS
https://bugs.kde.org/show_bug.cgi?id=439136 Bug ID: 439136 Summary: version 4.4.5 is damaged and won't open on MacOS Product: krita Version: 4.4.5 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: monica.fo...@gmail.com Target Milestone: --- SUMMARY Using Mac OSX 10.13.6. I downloaded the Krita .dmg, followed the installation steps, and when I tried to open the program for the first time, there was a loading bar that said it was "verifying" the program. Then I get the error " "Krita" is damaged and can't be opened. You should move it to the Trash." I deleted and re-downloaded the .dmg a few times and this happened every time. STEPS TO REPRODUCE 1. Download Mac version of Krita 4.4.5 2. Run installer 3. Open app OBSERVED RESULT App won't open and can't be used EXPECTED RESULT App would open and could be used SOFTWARE/OS VERSIONS Windows: macOS: 10.13.6 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.
