[digikam] [Bug 478222] AppImage 8.2.0 fails to start on Ubuntu 20.04: CXXABI_1.3.13 and GLIBCXX_3.4.29 not found
https://bugs.kde.org/show_bug.cgi?id=478222 --- Comment #2 from steph...@casco.net --- SUMMARY In a Debian 12.4 VirtualBox virtual machine I downloaded the AppImage 8.2.0. OBSERVED RESULT It worked as expected ADDITIONAL INFORMATION $ uname -a Linux debian12base 6.1.0-15-amd64 #1 SMP PREEMPT_DYNAMIC Debian 6.1.66-1 (2023-12-09) x86_64 GNU/Linux VirtualBox 6.1.48 r159471 (Qt5.15.2) VirtualBox Guest Additions: 6.1.48 -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 478424] New: Crash and Then Fails to Start
https://bugs.kde.org/show_bug.cgi?id=478424 Bug ID: 478424 Summary: Crash and Then Fails to Start Classification: Frameworks and Libraries Product: Akonadi Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: server Assignee: kdepim-b...@kde.org Reporter: joh...@member.fsf.org CC: c...@carlschwan.eu Target Milestone: --- Application: akonadiserver (5.24.3 (23.08.3)) Qt Version: 5.15.11 Frameworks Version: 5.111.0 Operating System: Linux 6.6.4-200.fc39.x86_64 x86_64 Windowing System: X11 Distribution: Fedora Linux 39 (KDE Plasma) DrKonqi: 5.27.9 [KCrashBackend] -- Information about the crash: I was checking my E-mail in the background, while I performed other tasks. When I returned to look at the mail, Akonadi had crashed. The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Akonadi Server (akonadiserver), signal: Segmentation fault [KCrash Handler] #4 0x56365b8d46ec in Akonadi::Server::PartStreamer::stream(bool, QByteArray const&, long long&, bool*) [clone .constprop.0] () #5 0x56365b80d937 in Akonadi::Server::ItemModifyHandler::parseStream() () #6 0x56365b7d71f2 in Akonadi::Server::Connection::parseStream(QSharedPointer const&) () #7 0x56365b7dabdd in Akonadi::Server::Connection::handleIncomingData() () #8 0x7fbf384df11b in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #9 0x7fbf384b457b in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #10 0x7fbf384b7a45 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #11 0x7fbf38506fef in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /usr/lib64/libQt5Core.so.5 #12 0x7fbf36712e5c in g_main_context_dispatch_unlocked.lto_priv () at /usr/lib64/libglib-2.0.so.0 #13 0x7fbf3676ddd8 in g_main_context_iterate_unlocked.isra () at /usr/lib64/libglib-2.0.so.0 #14 0x7fbf36710ad3 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #15 0x7fbf38506ad9 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #16 0x7fbf384b2f5b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #17 0x7fbf382f47b0 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #18 0x7fbf382f5bbd in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #19 0x7fbf37cac897 in start_thread () at /usr/lib64/libc.so.6 #20 0x7fbf37d336fc in clone3 () at /usr/lib64/libc.so.6 Thread 14 (Thread 0x7fbef97fa6c0 (LWP 23555) "0x56365d699140-"): #1 0x7fbf37cf708d in clock_gettime@GLIBC_2.2.5 () at /usr/lib64/libc.so.6 #2 0x7fbf36712a13 in g_main_context_prepare_unlocked.lto_priv () at /usr/lib64/libglib-2.0.so.0 #3 0x7fbf3676dbe0 in g_main_context_iterate_unlocked.isra () at /usr/lib64/libglib-2.0.so.0 #4 0x7fbf36710ad3 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #5 0x7fbf38506af6 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #6 0x7fbf384b2f5b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #7 0x56365b7db01c in Akonadi::Server::Connection::handleIncomingData() () #8 0x7fbf384df11b in QObject::event(QEvent*) () at /usr/lib64/libQt5Core.so.5 #9 0x7fbf384b457b in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib64/libQt5Core.so.5 #10 0x7fbf384b7a45 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib64/libQt5Core.so.5 #11 0x7fbf38506fef in postEventSourceDispatch(_GSource*, int (*)(void*), void*) () at /usr/lib64/libQt5Core.so.5 #12 0x7fbf36712e5c in g_main_context_dispatch_unlocked.lto_priv () at /usr/lib64/libglib-2.0.so.0 #13 0x7fbf3676ddd8 in g_main_context_iterate_unlocked.isra () at /usr/lib64/libglib-2.0.so.0 #14 0x7fbf36710ad3 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #15 0x7fbf38506ad9 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #16 0x7fbf384b2f5b in QEventLoop::exec(QFlags) () at /usr/lib64/libQt5Core.so.5 #17 0x7fbf382f47b0 in QThread::exec() () at /usr/lib64/libQt5Core.so.5 #18 0x7fbf382f5bbd in QThreadPrivate::start(void*) () at /usr/lib64/libQt5Core.so.5 #19 0x7fbf37cac897 in start_thread () at /usr/lib64/libc.so.6 #20 0x7fbf37d336fc in clone3 () at /usr/lib64/libc.so.6 Thread 13 (Thread 0x7fbefaffd6c0 (LWP 23523) "0x56365d695880-"): #1 0x7fbf3676dd74 in g_main_context_iterate_unlocked.isra () at /usr/lib64/libglib-2.0.so.0 #2 0x7fbf36710ad3 in g_main_context_iteration () at /usr/lib64/libglib-2.0.so.0 #3 0x7fbf38506af6 in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib64/libQt5Core.so.5 #4 0x7fbf384b2f5b in
[digikam] [Bug 478423] New: Rating assignment via UI or shortcut is not consistent
https://bugs.kde.org/show_bug.cgi?id=478423 Bug ID: 478423 Summary: Rating assignment via UI or shortcut is not consistent Classification: Applications Product: digikam Version: 8.1.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Tags-Rating Assignee: digikam-bugs-n...@kde.org Reporter: fa...@fabiosirna.com Target Milestone: --- Created attachment 164101 --> https://bugs.kde.org/attachment.cgi?id=164101=edit screenshot of the culling view In digikam 8.1.0, if two images (JPG+RAW) are in a group and have the same rating, in the setup I attach in the screenshot, there is inconsistent behavior: - if I click the star on the first thumbnail to downgrade from 3 to 2, only the JPG (first image in the stack) is updated (this is a bug); - if I press ctrl+2 to assign the rating via shortcut, both the JPG and RAW are updated correctly (this is the correct behavior). -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 478258] Crash when i click "Properites"
https://bugs.kde.org/show_bug.cgi?id=478258 --- Comment #3 from tagwer...@innerjoin.org --- (In reply to tagwerk19 from comment #2) >$ systemd --user start kde-baloo Sorry... $ systemctl --user start kde-baloo -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 478258] Crash when i click "Properites"
https://bugs.kde.org/show_bug.cgi?id=478258 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org --- Comment #2 from tagwer...@innerjoin.org --- (In reply to TYMA from comment #0) > ... > #5 0x7fd3d5a98b56 in mdb_env_open () at /usr/lib/liblmdb.so > #6 0x7fd3d7db30e9 in Baloo::Database::open(Baloo::Database::OpenMode) () > at /usr/lib/libKF5BalooEngine.so.5 > #7 0x7fd3da205d81 in Baloo::File::load() () at /usr/lib/libKF5Baloo.so.5 > ... It's trying to find/open the database - something that should be under ~/.local/share/baloo I think if the file's simply not there, you simply don't get any results. Maybe the file has been truncated/corrupted. Close down the baloo_file indexer, go to the folder and rename the "index" file. Something like: $ pkill baloo_file $ cd ~/.local/share/baloo $ mv index index.suspect I assume your Arch runs with systemd, so you can restart the indexing with: $ systemd --user start kde-baloo -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 478222] AppImage 8.2.0 fails to start on Ubuntu 20.04: CXXABI_1.3.13 and GLIBCXX_3.4.29 not found
https://bugs.kde.org/show_bug.cgi?id=478222 steph...@casco.net changed: What|Removed |Added CC||steph...@casco.net --- Comment #1 from steph...@casco.net --- SUMMARY I also downloaded the 8.2.0 AppImage and tried to start it, which fails. Earlier versions did not have an issue (I'm currently using the 7.10 AppImage). STEPS TO REPRODUCE 1. Download AppImage 8.2.0 on Debian 11.8 2. Start it in terminal OBSERVED RESULT Following error messages appear in the terminal: $ ./digiKam-8.2.0-x86-64.appimage -- digiKam Linux AppImage Bundle -- Use 'help' as CLI argument to know all available options for digiKam application. -- Notes: to integrate this bundle to your desktop, use AppImageLauncher. --to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'. --to extract the bundle contents locally, use option '--appimage-extract' on the command line. -- Detected host Linux -64- -- AppImage mounted directory: /tmp/.mount_digiKa7HKWwK Check library libudev.so.0 Check library libxcb-dri3.so.0 Check library libcrypto.so.1.1 Check library libssl.so.1.1 Check library libnss3.so Check library libnssutil3.so Check library libsmime3.so Check library libgmodule-2.0.so.0 Check library libgnutls.so.30 -- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1:/usr/lib/x86_64-linux-gnu/libssl.so.1.1:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0:/usr/lib/x86_64-linux-gnu/libgnutls.so.30 digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libMagick++-7.Q16.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libdigikamdatabase.so.8.2.0) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libdigikamcore.so.8.2.0) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libKF5CoreAddons.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libKF5ConfigCore.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libKF5Service.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libopencv_dnn.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libopencv_imgproc.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libopencv_ml.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libopencv_core.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libopencv_core.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libopencv_core.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libexiv2.so.28) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libheif.so.1) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `CXXABI_1.3.13' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libheif.so.1) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/liblensfun.so.2) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libopencv_imgcodecs.so.408) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libKF5ConfigWidgets.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libKF5KIOCore.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libKF5WindowSystem.so.5) digikam: /lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.29' not found (required by /tmp/.mount_digiKa7HKWwK/usr/lib/libde265.so) EXPECTED RESULT Digikam starts without complaining about missing libraries.
[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built
https://bugs.kde.org/show_bug.cgi?id=478416 --- Comment #4 from Robby Engelmann --- (gdb) bt #0 0x7fffe9f536de in Akonadi::ItemCreateJob::doStart() () at /lib64/libKPim6AkonadiCore.so.6 #1 0x7fffe9f59278 in () at /lib64/libKPim6AkonadiCore.so.6 #2 0x7fffebdcb2ae in QObject::event(QEvent*) (this=0x5607e930, e=0x7ffe840026a0) at /usr/src/debug/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qobject.cpp:1437 #3 0x7fffecfc094e in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x5607e930, e=0x7ffe840026a0) at /usr/src/debug/qtbase-everywhere-src-6.6.1/src/widgets/kernel/qapplication.cpp:3296 #4 0x7fffebd878b8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x5607e930, event=0x7ffe840026a0) at /usr/src/debug/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qcoreapplication.cpp:1121 #5 0x7fffebd878f9 in QCoreApplication::sendEvent(QObject*, QEvent*) (receiver=, event=) at /usr/src/debug/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qcoreapplication.cpp:1539 #6 0x7fffebd87c17 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) (receiver=0x0, event_type=0, data=0x555adee0) at /usr/src/debug/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qcoreapplication.cpp:1901 #7 0x7fffebfad9e3 in postEventSourceDispatch(GSource*, GSourceFunc, gpointer) (s=0x556051a0) at /usr/src/debug/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qeventdispatcher_glib.cpp:243 #8 0x7fffe8cb1f30 in () at /lib64/libglib-2.0.so.0 #9 0x7fffe8cb3b58 in () at /lib64/libglib-2.0.so.0 #10 0x7fffe8cb420c in g_main_context_iteration () at /lib64/libglib-2.0.so.0 #11 0x7fffebfabc6c in QEventDispatcherGlib::processEvents(QFlags) (this=0x555962e0, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.6.1/src/corelib/kernel/qeventdispatcher_glib.cpp:393 #12 0x7fffebd9211b in QEventLoop::exec(QFlags) (this=0x7fffc780, flags=...) at /usr/src/debug/qtbase-everywhere-src-6.6.1/build/include/QtCore/../../../src/corelib/global/qflags.h:34 #13 0x7fffebd8bd46 in QCoreApplication::exec() () at /usr/src/debug/qtbase-everywhere-src-6.6.1/build/include/QtCore/../../../src/corelib/global/qflags.h:74 #14 0x7fffec5e268c in QGuiApplication::exec() () at /usr/src/debug/qtbase-everywhere-src-6.6.1/src/gui/kernel/qguiapplication.cpp:1925 #15 0x7fffecfbdd85 in QApplication::exec() () at /usr/src/debug/qtbase-everywhere-src-6.6.1/src/widgets/kernel/qapplication.cpp:2574 #16 0x9138 in main(int, char**) (argc=, argv=) at /usr/src/debug/kmail-24.01.80git.20231211T021212~c1635d35/src/main.cpp:174 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 478141] Height of the window decrease after changing tabs
https://bugs.kde.org/show_bug.cgi?id=478141 --- Comment #7 from Wankupi <2893353...@qq.com> --- (In reply to Albert Astals Cid from comment #6) > Are you running a custom theme or style? I only changed the icons. After I change it back to default, this problem still occurs. (sorry for reply late) -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built
https://bugs.kde.org/show_bug.cgi?id=478416 --- Comment #3 from Robby Engelmann --- this is what shows up in konsole: >kmail qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "stateChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMState qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "connectivityChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMConnectivityState qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "deviceTypeChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMDeviceType qt.dbus.integration: Could not connect "org.freedesktop.NetworkManager" to "meteredChanged" : Type not registered with QtDBus in parameter list: QNetworkManagerInterface::NMMetered org.kde.pim.kmail_expertplugin: toggle_mimeparttree is not defined lstFilters 0 lstFilters 7 doh set to "" -- SystemOnly gpg.qgpgme: found no group for entry verbose of component "tpm2daemon" gpg.qgpgme: found no group for entry quiet of component "tpm2daemon" gpg.qgpgme: found no group for entry debug-level of component "tpm2daemon" gpg.qgpgme: found no group for entry log-file of component "tpm2daemon" *** KMail got signal 11 (Exiting) *** Dead letters dumped. KCrash: Application 'kmail' crashing... crashRecursionCounter = 2 Segmentation fault (core dumped) The crash occurred when trying to send an email -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built
https://bugs.kde.org/show_bug.cgi?id=478416 Robby Engelmann changed: What|Removed |Added CC||robby.engelmann@r-engelmann ||.de --- Comment #2 from Robby Engelmann --- BTW, there is also no pop3 working, but the ews ressource did its job -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 478285] Android phone not detected since updating to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=478285 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/frameworks/solid/-/merge_requests/151 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478422] Plasma crashed after hovering taskmanager app icon
https://bugs.kde.org/show_bug.cgi?id=478422 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 198260] LANGUAGE environment variable empty
https://bugs.kde.org/show_bug.cgi?id=198260 --- Comment #8 from nl6...@gmail.com --- I don't understand why I would need to create a new bug report if I'm having this exact issue exactly as the original reporter described it more than 14 years ago. This bug has obviously survived through multiple generations of KDE. $ cat /etc/locale.conf LANG=lv_LV.UTF-8 $ cat ~/.config/plasma-localerc [Formats] LANG=lv_LV.UTF-8 $ printenv | grep -E '^(LANG|LC_)' LANG=lv_LV.UTF-8 LANGUAGE= -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built
https://bugs.kde.org/show_bug.cgi?id=478416 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- Hi, backtrace please. Thanks -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 440066] Remote places not showing label in Places Panel when mounted through terminal
https://bugs.kde.org/show_bug.cgi?id=440066 E. F. Keebler changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- CC||kde@efkeebler.com --- Comment #16 from E. F. Keebler --- This same issue has affected me for a long time; I was glad to find it mentioned here, and puzzled that no one had ever followed up with a suggestion about the source of a label that could be used in place of the full path. In my case, I mount numerous remote folders via sshfs, and in Dolphin these show up under PLACES as the full local path to the mount-point I have selected, which is useless for differentiation as the key information is the folder name at the very end of the path (which is not visible as the path is much wider than the Places panel). Here's my point: Dolphin already knows the name of the innermost folder, which would make a far better label than the full path. If I right-click on the path and select Properties, up comes the Properties dialog showing the name of the folder (next to a folder icon), with the rest of the path given below (next to "Location"). If there were a user-accessible option for the Devices section to show the same name that is already given in the Properties dialog (when one exists), that would be a massive usability improvement in many cases. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478422] New: Plasma crashed after hovering taskmanager app icon
https://bugs.kde.org/show_bug.cgi?id=478422
Bug ID: 478422
Summary: Plasma crashed after hovering taskmanager app icon
Classification: Plasma
Product: plasmashell
Version: master
Platform: Compiled Sources
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: generic-crash
Assignee: plasma-b...@kde.org
Reporter: jpe...@petsovits.com
Target Milestone: 1.0
Application: plasmashell (5.90.90)
(Compiled from sources)
Qt Version: 6.6.1
Frameworks Version: 5.247.0
Operating System: Linux 6.6.3-arch1-1 x86_64
Windowing System: Wayland
Distribution: "Arch Linux"
DrKonqi: 5.90.90 [CoredumpBackend]
-- Information about the crash:
Rebuilt all the workspace repos (incl. dependencies) from source today. Last
time I pulled the whole set was perhaps one and a half weeks ago? I did not
notice the crash then, so something probably changed in the meantime.
The crash happens reproducibly for me when simply hovering an application icon
in the taskmanager applet, e.g. Dolphin or Firefox, without the app actually
running at the time of hover. I figure it wants to set up screencasts for the
app/window info popup, and fails, running into this assertion.
The crash itself comes from Q_ASSERT(isInitialized());
in plasma-workspace/libtaskmanager/declarative/screencasting.cpp,
constructor of ScreencastingPrivate which is a QWaylandClientExtensionTemplate
for QtWayland::zkde_screencast_unstable_v1.
That code in particular was introduced in 2022, so it's more likely some kind
of interaction issue.
I'm also aware that my Plasma 6 installation suffers from some kind of
inability to get many or perhaps all KAuth calls successfully working. Root
cause analysis pending. I would not in the least be surprised if this were the
underlying reason for ScreencastingPrivate not being able to initialize. Note
that I nuked my entire build prefix and ~/.cache just to make sure, however I
did not start the entire build from scratch. I'll ask for help regarding my
KAuth issue and see if a potential fix for that will also mitigate this crash.
But again, it wasn't there two weeks ago and the only thing I had going on then
was libtaskmanager not being able to get info from open windows from KWin.
So perhaps not the highest-priority crash, given my setup's deficiencies. But
perhaps libtaskmanager could gracefully disable this functionality instead of
crashing, if the screencasting extension does happen to fail initializing?
The crash can be reproduced every time.
-- Backtrace:
Application: plasmashell (plasmashell), signal: Aborted
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = 0x0}
[New LWP 185768]
[New LWP 185794]
[New LWP 185798]
[New LWP 185799]
[New LWP 185795]
[New LWP 185800]
[New LWP 185784]
[New LWP 185814]
[New LWP 186010]
[New LWP 185802]
[New LWP 185804]
[New LWP 185801]
[New LWP 186060]
[New LWP 186002]
[New LWP 186003]
[New LWP 186065]
[New LWP 185803]
[New LWP 185812]
[New LWP 186049]
[New LWP 186016]
[New LWP 186066]
[New LWP 186012]
[New LWP 186053]
[New LWP 186014]
[New LWP 186050]
[New LWP 186011]
[New LWP 186064]
[New LWP 186013]
[New LWP 186062]
[New LWP 185811]
[New LWP 185882]
[New LWP 185813]
[New LWP 186063]
[New LWP 186015]
[New LWP 186061]
[New LWP 186067]
[New LWP 186022]
This GDB supports auto-downloading debuginfo from the following URLs:
Enable debuginfod for this session? (y or [n]) [answered N; input not from
terminal]
Debuginfod has been disabled.
To make this setting permanent, add 'set debuginfod enabled off' to .gdbinit.
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib/libthread_db.so.1".
Core was generated by `/home/kpetso/build/kde6/prefix/bin/plasmashell
--no-respawn'.
Program terminated with signal SIGABRT, Aborted.
#0 0x7fc8f26ac83c in ?? () from /usr/lib/libc.so.6
[Current thread is 1 (Thread 0x7fc8ee1e7a40 (LWP 185768))]
Cannot QML trace cores :(
[Current thread is 1 (Thread 0x7fc8ee1e7a40 (LWP 185768))]
Thread 37 (Thread 0x7fc884dfa6c0 (LWP 186022)):
#0 0x7fc8f26a74ae in () at /usr/lib/libc.so.6
#1 0x7fc8f26a9d40 in pthread_cond_wait () at /usr/lib/libc.so.6
#2 0x7fc8e56d1b5c in () at /usr/lib/dri/iris_dri.so
#3 0x7fc8e571ca0c in () at /usr/lib/dri/iris_dri.so
#4 0x7fc8f26aa9eb in () at /usr/lib/libc.so.6
#5 0x7fc8f272e7cc in () at /usr/lib/libc.so.6
Thread 36 (Thread 0x7fc833fff6c0 (LWP 186067)):
#0 0x7fc8f27214c6 in ppoll () at /usr/lib/libc.so.6
#1 0x7fc8f2ec21eb in qt_safe_poll(pollfd*, unsigned long, timespec const*)
() at /usr/lib/libQt6Core.so.6
#2 0x7fc8f3c5b768 in () at /usr/lib/libQt6Network.so.6
#3 0x7fc8f3c07339 in () at /usr/lib/libQt6Network.so.6
#4 0x7fc8f3bff6ee in QAbstractSocket::waitForReadyRead(int) () at
/usr/lib/libQt6Network.so.6
#5
[plasmashell] [Bug 468863] Plasma automatically switching from unoccupied desktops to occupied desktops
https://bugs.kde.org/show_bug.cgi?id=468863 --- Comment #7 from Alex --- Hi, I switched to Arch Linux and the issue disappeared for a while, but now it's back. I manage my home directory with nix home-manager and my /etc directory and others with aconfmgr, so I was able to roll back the vast majority of my files to before the issue happened as well as delete and regenerate all my ~/.config/*rc files, but none of those things made the issue go away. I noticed before the issue started happening 24/7 that it would only happen if I set a splash screen on kde (which doesn't play nicely with i3). Setting splash screen to "None" repeatedly made the issue go away (although unfortunately that doesn't work anymore for some reason). Interestingly, even after the splash screen disappeared, the issue persisted until I logged out and back in again. Not sure what the deal is there. I figured maybe there was an urgent window or something, but I dumped the whole x window tree and I don't see anything marked as urgent. I also tried running plasmashell through x11trace and I'm seeing some extra stuff happen with _NET_CURRENT_DESKTOP when I try to switch to an empty workspace, although I couldn't get much useful information beyond that. I'm willing to put a lot more effort into debugging this further, but I'm just not sure where to look next. Does anyone have any ideas? -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 441405] Segmentation fault on pressing the 'Zoom' or 'Browse'
https://bugs.kde.org/show_bug.cgi?id=441405 --- Comment #3 from Nicolas Mailloux --- Created attachment 164100 --> https://bugs.kde.org/attachment.cgi?id=164100=edit New crash information added by DrKonqi kile (2.9.93) using Qt 5.15.11 Kile crashes when clicking 'Browse' button -- Backtrace (Reduced): #4 0xfffeec292d88 in PageViewAnnotator::detachAnnotation() () from /usr/lib64/qt5/plugins/okularpart.so #5 0x064f72bc [PAC] in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #6 0x06fcaea4 [PAC] in QAction::triggered(bool) () from /lib64/libQt5Widgets.so.5 #7 0x06fce210 [PAC] in QAction::activate(QAction::ActionEvent) () from /lib64/libQt5Widgets.so.5 #8 0x070c68a0 [PAC] in QAbstractButtonPrivate::click() () from /lib64/libQt5Widgets.so.5 -- You are receiving this mail because: You are watching all bug changes.
[kile] [Bug 441405] Segmentation fault on pressing the 'Zoom' or 'Browse'
https://bugs.kde.org/show_bug.cgi?id=441405 Nicolas Mailloux changed: What|Removed |Added CC||nicolecriv...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470983] After update from plasma5 2.24.4 to 5.27.4, when not using Systemd boot, scripts executed in virtual consoles cannot change directory
https://bugs.kde.org/show_bug.cgi?id=470983 --- Comment #9 from davejpla...@gmail.com --- (In reply to Nate Graham from comment #8) > Actually, let me ask for clarification on something. Are you using virtual > terminals for this? Or are you just running `mc` in a regular terminal app > like Konsole? I experience this bug in any terminal app running under kde. I use konsole exclusively but it happens in xterm or any other terminal app. It doesn't happen in xfce or icewm or a virtual console, it only happens under kde and the change in behavior causes scripts executed in the terminal app to be restricted to a private shell and this causes the mc shell script to fail. Another consequence is: https://bugzilla.suse.com/show_bug.cgi?id=1213156 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477391] Black box instead of zoom when using magnify effect for window contents
https://bugs.kde.org/show_bug.cgi?id=477391 Justin Zobel changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED --- Comment #3 from Justin Zobel --- I can't reproduce it on my laptop. It was likely on my desktop. I'll check at some point again in the near future when I have 6 on my desktop again. -- You are receiving this mail because: You are watching all bug changes.
[drkonqi] [Bug 477586] FR: run application through gdb to actually get the debug symbols, otherwise backtraces fail
https://bugs.kde.org/show_bug.cgi?id=477586 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 460569] KOrganizer crashed on creating a new task
https://bugs.kde.org/show_bug.cgi?id=460569 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[ktorrent] [Bug 388966] Enabling "Search" plugin freezes KTorrent application
https://bugs.kde.org/show_bug.cgi?id=388966 Bug Janitor Service changed: What|Removed |Added Resolution|FIXED |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #26 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kfilemetadata] [Bug 453148] Elisa crashes in KFileMetaData::EmbeddedImageData::imageData() shortly after launch
https://bugs.kde.org/show_bug.cgi?id=453148 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477257] "Apply Settings" dialog scrolls unnecessarily
https://bugs.kde.org/show_bug.cgi?id=477257 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 477525] XML file is not saved if......
https://bugs.kde.org/show_bug.cgi?id=477525 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 460671] Key board shortcut setting only take bindings with modifiers.
https://bugs.kde.org/show_bug.cgi?id=460671 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 454110] Cannot pan/zoom/rotate by using ctrl/shift
https://bugs.kde.org/show_bug.cgi?id=454110 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[palapeli] [Bug 477452] 1500 piece puzzle crashes. Exported backup file doesn't include latest status
https://bugs.kde.org/show_bug.cgi?id=477452 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477391] Black box instead of zoom when using magnify effect for window contents
https://bugs.kde.org/show_bug.cgi?id=477391 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477368] Moving panels between screens through Manage Desktops and Panels dialog causes graphical corruption on them
https://bugs.kde.org/show_bug.cgi?id=477368 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 459305] Krita 5.1: Canvas Input selection tools (and others) set to modifier keys (ctrl, shift & alt) do not respond as expected.
https://bugs.kde.org/show_bug.cgi?id=459305 --- Comment #18 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 466658] EXIF metadata is used when available for JPEG thumbnails, resulting to low resolution thumbnails
https://bugs.kde.org/show_bug.cgi?id=466658 --- Comment #16 from Stéphane Tréboux --- kio-extras 23.08.3 including Git commit 8a0c0d97 is now available as a Ubuntu package targeting the upcoming Ubuntu 24.04 (noble). If you use Ubuntu 23.10 (mantic) on AMD64 you can download and install at your own risk, please only use if you know what you are doing! https://packages.ubuntu.com/noble/amd64/kio-extras/download https://packages.ubuntu.com/noble/all/kio-extras-data/download https://packages.ubuntu.com/noble/amd64/libkf5kexiv2-15.0.0/download Here are the direct download links I used due to https://packages.ubuntu.com/ being often down lately: https://cz.archive.ubuntu.com/ubuntu/pool/universe/k/kio-extras/kio-extras_23.08.3-0ubuntu1_amd64.deb https://cz.archive.ubuntu.com/ubuntu/pool/universe/k/kio-extras/kio-extras-data_23.08.3-0ubuntu1_all.deb https://cz.archive.ubuntu.com/ubuntu/pool/universe/libk/libkf5kexiv2/libkf5kexiv2-15.0.0_23.08.3-0ubuntu1_amd64.deb Once you have downloaded the three packages (kio-extras, kio-extras-data and libkf5kexiv2-15.0.0) in the new version you can use "dpkg -i *.deb" to install them in one batch from a command line. After installation go to ~/.cache and rename the folder "thumbnails" to "thumbnails_bak". If you are happy with the result you can erase the folder later on. No restart is needed and applications like the file manager Dolphin will immediately generate new thumbnails. The new thumbnail will not be the embedded exif thumbnail when it is too small to be used. The criteria applied is that the exif thumbnail will be used if at least one of the edges is long enough. In other words, both the width and height of the exif thumbnail need to be strictly smaller than the target size for the desired thumbnail for the exif thumbnail to be skipped. The target size of the thumbnail is configurable in many apps, in Dolphin there is a slider at the bottom right. If you pick a large enough value there is a good chance that the exif thumbnail will never be used. This will not necessarily resolve issues like the wrong orientation of the thumbnail (https://bugs.kde.org/attachment.cgi?id=160117), especially if the exif thumbnail comes with a sufficient resolution (https://bugsfiles.kde.org/attachment.cgi?id=156871). If you have to go back to stock Ubuntu 23.10 for any reason, the packages which originally come with Ubuntu 23.10 can be downloaded and installed the same way as the packages from Ubuntu 24.04. https://packages.ubuntu.com/mantic/amd64/kio-extras/download https://packages.ubuntu.com/mantic/all/kio-extras-data/download https://packages.ubuntu.com/mantic/amd64/libkf5kexiv2-15.0.0/download Here are the direct download links I used due to https://packages.ubuntu.com/ being often down lately: https://cz.archive.ubuntu.com/ubuntu/pool/universe/k/kio-extras/kio-extras_23.08.1-0ubuntu1_amd64.deb https://cz.archive.ubuntu.com/ubuntu/pool/universe/k/kio-extras/kio-extras-data_23.08.1-0ubuntu1_all.deb https://cz.archive.ubuntu.com/ubuntu/pool/universe/libk/libkf5kexiv2/libkf5kexiv2-15.0.0_23.08.1-0ubuntu1_amd64.deb Again, once you have downloaded the three packages (kio-extras, kio-extras-data and libkf5kexiv2-15.0.0) in the original version you can use "dpkg -i *.deb" to install them in one batch from a command line. After installation go to ~/.cache, erase the folder "thumbnails" and rename the folder "thumbnails_bak" to "thumbnails". -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477486] Ark not built with Qt6
https://bugs.kde.org/show_bug.cgi?id=477486 Carlos De Maine changed: What|Removed |Added CC||carlosdema...@gmail.com --- Comment #14 from Carlos De Maine --- neon's policy is to package qt6 apps when master is qt6 only, thus ark is still qt5 in unstable. however experimental which builds on top unstable has alpha qt6 apps including ark. installing the neon-settings-experimental package will upgrade any qt5 apps installed that have a qt6 variant in the experimental archive. or manually install the ark deb from https://archive.neon.kde.org/experimental/pool/main/a/ark/ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 453386] Multi/hybrid GPU double copy
https://bugs.kde.org/show_bug.cgi?id=453386 quangngo changed: What|Removed |Added CC||ngoquang2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 477644] Implement tear-off windows so multiple documents can be visible simultaneously
https://bugs.kde.org/show_bug.cgi?id=477644 Dave92f1 changed: What|Removed |Added Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #4 from Dave92f1 --- (In reply to Christoph Cullmann from comment #3) > You can do that, right click on a tab, detach document. Thanks. That's better than nothing, but not the preferred UI. Left-drag the tab out of the kate window (as gedit does it) would be better. For the wishlist, please. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478418] Clicking with a pixel brush in some places doesn't work
https://bugs.kde.org/show_bug.cgi?id=478418 Freya Lupen changed: What|Removed |Added Ever confirmed|0 |1 Keywords||regression CC||penguinflyer2...@gmail.com Status|REPORTED|CONFIRMED --- Comment #1 from Freya Lupen --- Confirmed. Additionally, if Sharpness->'Align the brush preview outline to the pixel grid' is checked in the brush's settings, then clicking near the corner of a pixel still behaves as expected. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478421] The panel disappeared after entering full screen mode in GNOME Boxes VMs
https://bugs.kde.org/show_bug.cgi?id=478421 Matt Fagnani changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478421] New: The panel disappeared after entering full screen mode in GNOME Boxes VMs
https://bugs.kde.org/show_bug.cgi?id=478421 Bug ID: 478421 Summary: The panel disappeared after entering full screen mode in GNOME Boxes VMs Classification: Plasma Product: kwin Version: 5.90.0 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: matt.fagn...@bell.net Target Milestone: --- Created attachment 164099 --> https://bugs.kde.org/attachment.cgi?id=164099=edit Recording of panel disappearing when entering full screen mode in GNOME Boxes QEMU/KVM VM with hardware acceleration enabled SUMMARY I booted the Fedora Rawhide/40 KDE Plasma live image Fedora-KDE-Live-x86_64-Rawhide-20231211.n.0.iso in GNOME Boxes QEMU/KVM VMs in a Fedora 39 KDE Plasma host using Plasma 5.27.9 on Wayland. To work around the VM getting stuck on the Plasma 5.27.80 splash screen as I reported at https://bugs.kde.org/show_bug.cgi?id=477643 I changed to VT2 by using the keyboard menu in the top bar of GNOME Boxes and selecting Ctrl+Alt+F2. When I changed back to VT1, Plasma was shown with the Plasma Welcome program open. I had GNOME Boxes shown as a maximized window. I entered full screen mode in the VM by selecting the full screen button in the GNOME Boxes top bar. The resolution appeared to increase vertically, but the visible area Plasma was shown in remained the same as in the maximized window. There were black bars at the top and bottom of the screen where Plasma wasn't shown. The panel disappeared in full screen mode as a result. There were spice-vdagent errors repeated in the journal in which it appeared to be trying to connect to mutter by dbus which was odd. Dec 11 18:42:07 spice-vdagent[2053]: display: failed to call GetCurrentState from mutter over DBUS Dec 11 18:42:07 spice-vdagent[2053]:error message: Cannot invoke method; proxy is for the well-known name org.gnome.Mutter.DisplayConfig without an owner, and proxy was constructed with the G_DBUS_PROXY_FLAGS_DO_NOT_AUTO_START flag Dec 11 18:42:07 spice-vdagent[2053]: No guest output map, using output index as display id Dec 11 18:42:07 kernel: input: spice vdagent tablet as /devices/virtual/input/input16 This problem happened every time I tried it. I'm attaching a recording of the problem with these errors shown in Konsole. After I exited full screen mode, the panel was shown again. I stopped spice-vdagent with sudo systemctl stop spice-vdagentd.service spice-vdagentd.socket The problem didn't happen when entering full screen mode after I stopped spice-vdagentd and those errors didn't occur. spice-vdagent crashed when I stopped it. STEPS TO REPRODUCE 1. Boot a Fedora 39 KDE Plasma installation updated to 2023-12-11 with updates-testing enabled 2. Log in to Plasma 5.27.9 on Wayland 3. Start Konsole 4. Install GNOME Boxes if it isn't already with sudo dnf install gnome-boxes 5. Download Fedora-KDE-Live-x86_64-Rawhide-20231211.n.0.iso from https://koji.fedoraproject.org/koji/buildinfo?buildID=2332213 6. Start GNOME Boxes 7. Boot Fedora-KDE-Live-x86_64-Rawhide-20231211.n.0.iso in a GNOME Boxes QEMU/KVM VM with 3 GiB RAM, UEFI enabled, and 3D acceleration disabled or enabled in a maximized window 8. To work around https://bugs.kde.org/show_bug.cgi?id=477643, switch to VT2 in GNOME boxes via the keyboard menu Ctrl+Alt+F2 and back to VT1 with Ctrl+Alt+F1 9. Enter full screen mode in GNOME Boxes by selecting the full screen button in its top bar OBSERVED RESULT The panel disappeared after entering full screen mode in GNOME Boxes VMs EXPECTED RESULT The panel should've remained visible after entering full screen mode SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora Rawhide/40 (available in About System) KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.1 ADDITIONAL INFORMATION This problem didn't happen if I selected full screen mode in GNOME Boxes before Plasma started, but Plasma froze when exiting full screen mode with some of the same spice-vdagent errors as I reported at https://bugs.kde.org/show_bug.cgi?id=478019 The problem didn't happen when using virt-manager QEMU/KVM VMs with the same image and settings. Plasma 5.27.80 had the problem. I don't think this problem happened with Plasma 5.27.9. The problem might've involved how Plasma interacted with spice-vdagent in GNOME Boxes specifically. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478419] Krita crashes immediately when trying to make a brush with the Random Pick filter, am able to adjust settings on other filters
https://bugs.kde.org/show_bug.cgi?id=478419 Freya Lupen changed: What|Removed |Added Status|REPORTED|CONFIRMED Ever confirmed|0 |1 CC||penguinflyer2...@gmail.com Keywords||regression --- Comment #1 from Freya Lupen --- Confirmed, and not specific to this filter. After switching filters, trying to change the settings crashes, because the UI still shows the settings for the previously selected filter instead of the new one. Switching to a different brush and back again reloads the settings and it works fine. This is a regression compared to 5.1.5. Example crash backtrace: > 0 QtCore 0x106288b58 > QObject::killTimer(int) + 36 > 1 QtCore 0x1062986fc QTimer::stop() + 32 > 2 libkritawidgetutils.20.0.0.dylib 0x1043b25e4 > KisParseSpinBoxPrivate::hideWarning() > const + 32 (kis_parse_spin_box_p.h:265) > 3 libkritawidgetutils.20.0.0.dylib 0x1043b092c > KisParseSpinBoxPrivate QDoubleSpinBox>::setValue(double, bool) + 192 (kis_parse_spin_box_p.h:95) > 4 libkritawidgetutils.20.0.0.dylib 0x1043b9400 > KisSliderSpinBoxPrivate KisDoubleParseSpinBox>::setValue(double, bool, bool, bool) + 112 > (kis_slider_spin_box_p.h:223) > 5 libkritawidgetutils.20.0.0.dylib 0x1043bed04 > KisSliderSpinBoxPrivate KisDoubleParseSpinBox>::lineEditMouseMoveEvent(QMouseEvent*) + 516 > (kis_slider_spin_box_p.h:808) > 6 QtCore 0x106260fec > QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) + > 264 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477866] Media Player applet reloads the cover art on opening
https://bugs.kde.org/show_bug.cgi?id=477866 Fushan Wen changed: What|Removed |Added Version Fixed In||6.0 Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/19c21597a16205e6a29f3f7a4 ||28818078cd742b5 Status|ASSIGNED|RESOLVED --- Comment #3 from Fushan Wen --- Git commit 19c21597a16205e6a29f3f7a428818078cd742b5 by Fushan Wen. Committed on 12/12/2023 at 01:48. Pushed by fusionfuture into branch 'master'. applets/mediacontroller: disable geometry timer when widget is not expanded The geometry of the stack view will change during expansion, which causes unnecessary reloading of the same image. FIXED-IN: 6.0 M +12 -4 applets/mediacontroller/package/contents/ui/AlbumArtStackView.qml M +6-5 applets/mediacontroller/package/contents/ui/ExpandedRepresentation.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/19c21597a16205e6a29f3f7a428818078cd742b5 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478420] New: Google-Earth Pro window will not show up
https://bugs.kde.org/show_bug.cgi?id=478420 Bug ID: 478420 Summary: Google-Earth Pro window will not show up Classification: Plasma Product: kwin Version: 5.90.0 Platform: Other OS: Linux Status: REPORTED Keywords: qt6, wayland Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: dougsha...@protonmail.com Target Milestone: --- 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 google-earth-pro .deb from Google's website via Discover 2. start Google Earth Pro in a Wayland session 3. Observe blank screen OBSERVED RESULT No window is visible, bit panels act as if a window is there- dodging if set to dodge, going from floating to normal if set to float. Google Earth Pro turns up in Task Switcher, but window won't be visible when switched to it. EXPECTED RESULT Google Earth Pro shows up as normal SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Neon Unstable (available in About System) KDE Plasma Version: 5.90.0 KDE Frameworks Version: 5.246.0 Qt Version: 6.6.0 ADDITIONAL INFORMATION Google Earth Pro works fine in X11 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 476670] Dolphin doesn't focus on the new pasted file if it's beyond screen border
https://bugs.kde.org/show_bug.cgi?id=476670 Felix Ernst changed: What|Removed |Added CC||felixer...@kde.org --- Comment #4 from Felix Ernst --- Everything is clear. Thank you for the report! We are just not that fast to look into it. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478256] Panel in dodge window mode appears in front of window after display configuration changes, including rotation, and resolution and scale changes
https://bugs.kde.org/show_bug.cgi?id=478256 --- Comment #17 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/1917 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478413] Reconnecting a monitor causes the super key shortcut for application launcher to stop working
https://bugs.kde.org/show_bug.cgi?id=478413 --- Comment #2 from Nora --- I've tried checking the journalctl while doing an unplug/replug to see if it produces anymore useful information. Also I'm not sure if this is a new thing or a different thing, but when the screen locked and I logged back in I no longer had a panel, I got a notification plasma shell has crashed and offered me to send a crash report (I did), the panel eventually appeared again but once again the super key was not working. Also one more thing to note is when I disconnect the primary monitor I no longer have a panel on my connected monitor. I don't know if that's intended or not. Dec 11 17:24:01 fedora plasmashell[2225]: file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78: TypeError: Type error Dec 11 17:24:09 fedora plasmashell[2225]: file:///usr/share/plasma/plasmoids/org.kde.plasma.digitalclock/contents/ui/main.qml:78: TypeError: Type error Dec 11 17:24:09 fedora systemd[1909]: drkonqi-coredump-pickup.service: start-pre operation timed out. Terminating. Dec 11 17:24:09 fedora systemd[1909]: drkonqi-coredump-pickup.service: Control process exited, code=killed, status=15/TERM Dec 11 17:24:09 fedora systemd[1909]: drkonqi-coredump-pickup.service: Failed with result 'timeout'. Dec 11 17:24:09 fedora systemd[1909]: Failed to start drkonqi-coredump-pickup.service - Consume pending crashes using DrKonqi. Dec 11 17:24:31 fedora plasmashell[2225]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken. Dec 11 17:24:31 fedora plasmashell[2225]: kf.plasma.quick: Exposed with no visual parent. Window positioning broken. Dec 11 17:24:37 fedora plasmashell[2225]: file:///usr/share/plasma/shells/org.kde.plasma.desktop/contents/views/Panel.qml:118:5: QML Connections: Detected function "onActivated" in Connections element. This is probably intended to be a signal handler but no signal of the target matches the name. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448866] [NVIDIA] Graphical glitches and unresponsive after waking from sleep
https://bugs.kde.org/show_bug.cgi?id=448866 Jean-Francois Roy changed: What|Removed |Added CC||j...@devklog.net -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475605] On X11 with NVIDIA GPU and proprietary driver, black screen with only cursor shown on wake from sleep
https://bugs.kde.org/show_bug.cgi?id=475605 Jean-Francois Roy changed: What|Removed |Added CC||j...@devklog.net --- Comment #15 from Jean-Francois Roy --- For what it's worth, I get this issue with the KDE Plasma 6.0 Beta 1 release (as installed by arch's kde-unstable repo) using Wayland. I'm trying to capture logs to file a report. It does not happen with the stable KDE Plasma release. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478333] Random stutters while gaming on Wayland session.
https://bugs.kde.org/show_bug.cgi?id=478333 --- Comment #3 from siamlig...@protonmail.com --- (In reply to fanzhuyifan from comment #1) > What GPU do you use? I use a 2200G APU. It's basically a CPU+GPU combo, the graphics are Vega 8 Integrated. I don't have a dedicated GPU. (In reply to fanzhuyifan from comment #2) > Possible duplicate of 474725 I don't see a mention of any particular load in that report. For me, it only happens specifically while gaming and only in a few games. I don't get it while browsing or doing productivity tasks. -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 478403] Broken Camera & Screenshare Portal
https://bugs.kde.org/show_bug.cgi?id=478403
Henning changed:
What|Removed |Added
Status|NEEDSINFO |RESOLVED
Resolution|WAITINGFORINFO |WORKSFORME
--- Comment #3 from Henning ---
It doesnt do anything. Signal Desktop would open the portal interface, you
would select the screen and tadaa signal shows your screen. Same on BBB, it
just says "no camera found" etc, as the portal is not opening
dec 12 00:39:30 PC xdg-desktop-portal-kde[2069]:
file:///usr/lib64/qt5/qml/org/kde/plasma/workspace/dialogs/SystemDialog.qml:103:5:
QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15
after any QtQuick imports and set
the restoreMode of the binding
to fix this warning.
In Qt < 6.0 the default is
Binding.RestoreBinding.
In Qt >= 6.0 the default is
Binding.RestoreBindingOrValue.
Binding {
^
dec 12 00:39:30 PC xdg-desktop-portal-kde[2069]:
file:///usr/lib64/qt5/qml/org/kde/plasma/workspace/dialogs/SystemDialog.qml:103:5:
QML Binding: Not restoring previous value because restoreMode has not been set.
This behavior is deprecated.
You have to import QtQml 2.15
after any QtQuick imports and set
the restoreMode of the binding
to fix this warning.
In Qt < 6.0 the default is
Binding.RestoreBinding.
In Qt >= 6.0 the default is
Binding.RestoreBindingOrValue.
dec 12 00:39:34 PC xdg-desktop-portal-kde[2069]: kpipewire_logging: Window not
available PipeWireSourceItem(0x562b0f854020, parent=0x562b0f41d080,
geometry=0,0 199x150)
dec 12 00:39:34 PC kwin_wayland[1896]: kf.service.services: The desktop entry
file "/var/home/user/.local/share/applications/ODV-Manual.desktop" has Type=
"Application" but has no Exec field.
dec 12 00:39:34 PC kwin_wayland[1896]: kf.service.services: The desktop entry
file "/usr/share/applications/org.freedesktop.Xwayland.desktop" has Type=
"Application" but has no Exec field.
dec 12 00:39:34 PC kwin_wayland[1896]: kf.service.services: The desktop entry
file "/usr/share/applications/qemu.desktop" has Type= "Application" but has no
Exec field.
dec 12 00:39:34 PC kwin_wayland[1896]: kf.service.services: The desktop entry
file "/var/home/user/.local/share/applications/ODV.desktop" has Type=
"Application" but has no Exec field.
dec 12 00:39:34 PC plasmashell[3712]: 'loop->recurse > 0' failed at
../src/pipewire/thread-loop.c:426 pw_thread_loop_wait()
dec 12 00:39:37 PC xdg-desktop-portal-kde[2069]: kpipewire_logging: Window not
available PipeWireSourceItem(0x562b0f87acb0, parent=0x562b0fb343d0,
geometry=0,0 223x150)
dec 12 00:39:46 PC plasmashell[3712]: [Parent 3712, Main Thread] WARNING:
invalid (NULL) pointer instance: 'glib warning', file
/builddir/build/BUILD/firefox-120.0.1/toolkit/xre/nsSigHandlers.cpp:187
dec 12 00:39:46 PC plasmashell[3712]: [Parent 3712, Main Thread] WARNING:
g_signal_emit_by_name: assertion 'G_TYPE_CHECK_INSTANCE (instance)' failed:
'glib warning', file
/builddir/build/BUILD/firefox-120.0.1/toolkit/xre/nsSigHandlers.cpp:187
dec 12 00:39:46 PC firefox[3712]: invalid (NULL) pointer instance
dec 12 00:39:46 PC firefox[3712]: g_signal_emit_by_name: assertion
'G_TYPE_CHECK_INSTANCE (instance)' failed
dec 12 00:39:46 PC plasmashell[2018]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/PlasmoidItem.qml:125:
TypeError: Cannot read property 'compactRepresentationItem' of null
dec 12 00:39:46 PC plasmashell[2018]:
file:///usr/share/plasma/plasmoids/org.kde.plasma.private.systemtray/contents/ui/items/PlasmoidItem.qml:125:
TypeError: Cannot read property 'compactRepresentationItem' of null
Weird, I cannot reproduce this after a reboot.
Will set as worksforme until it happens again
--
You are receiving this mail because:
You are watching all bug changes.
[k3b] [Bug 253768] Error when trying to open the filetype options while ripping audio CD.
https://bugs.kde.org/show_bug.cgi?id=253768 --- Comment #13 from Julius R. --- (In reply to Albert Astals Cid from comment #12) > But you want to change it while the ripping is happening or from that dialog > before the ripping has started? Before, of course... -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 451158] With display scaling, incorrect cursor scaling on non-XWayland-using GTK and Electron apps due to their lack of support for the cursor-shape-v1 protocl
https://bugs.kde.org/show_bug.cgi?id=451158 Jin Liu changed: What|Removed |Added CC||ad.liu@gmail.com --- Comment #11 from Jin Liu --- (In reply to Nate Graham from comment #7) > So there are three options here. > > 1. Wait until GTK gains support for the cursor-shape-v1 protocol > 2. Patch all cursor themes in existence to have sizes for all possible scale > factors (we just did this for KDE's Breeze cursors) > 3. Automatically scale cursors as needed in KWin > > --- > > Downside of #1 is that it's up to toolkit developers outside of KDE. > > Downside of #2 is that it's up theme authors outside of KDE, and therefore > really not feasible at all. > > Downsides of #3 include: > - It's a hack/workaround due to lack of proper support for a public standard > in other toolkits > - Scaling cursors would introduce blurriness, so the result wouldn't be > pixel-perfect in comparison to parts of the system written in toolkits that > do implement the cursor-shape-v1 protocol, therefore it wouldn't actually > fix the bug. Downside of #2 also: We patched Breeze cursors only for 24px. It won't work if the user selected a larger cursor size. (Unless we remove the ability to select cursor size in systemsettings) About #3: The cursor-shape-v1 protocol would have to scale cursors in kwin anyway, so the same code can be reused and yield same results. If we are to continue supporting X11 apps, and if we can't expect all Wayland apps beside KDE/GTK/Electron to use the cursor-shape-v1 protocol, then we have to implement this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477498] Panels margins separator became large/wide
https://bugs.kde.org/show_bug.cgi?id=477498 ratijas changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 from ratijas --- It don't happen anymore. Let's assume it was fixed by some recent change. For the record, it not specific to Oxygen. I just switched themes to make sure that it was not a Breeze theme bug in the first place! -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 456482] hardware decoding doesn't work
https://bugs.kde.org/show_bug.cgi?id=456482 --- Comment #20 from sunsp...@gmail.com --- I've been trying to edit the org.kde.haruna.desktop file where this line is: Exec=/usr/bin/flatpak run --branch=stable --arch=x86_64 --command=haruna --file-forwarding org.kde.haruna @@u %u @@ No matter what I try, I can't get it to stick.. --env doesn't work, etc. -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 253768] Error when trying to open the filetype options while ripping audio CD.
https://bugs.kde.org/show_bug.cgi?id=253768 --- Comment #12 from Albert Astals Cid --- But you want to change it while the ripping is happening or from that dialog before the ripping has started? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478400] Minimizing apps with the task manager sometimes doesn't work
https://bugs.kde.org/show_bug.cgi?id=478400 --- Comment #2 from Paragoumba --- (In reply to Nate Graham from comment #1) > Does it *sometimes* not work, or *always* not work? > > Do the apps for which it doesn't work have multiple windows open? > > Can you run `journalctl -f` and see if something it printed there when you > try to minimnize an app by clicking on it and it doesn't work? > > Can you plug in an external mouse (or a different mouse) to see if that > helps? > > Do you have an NVIDIA GPU? It sometimes doesn't work, it seems to work again after interacting with other windows/screens. I don't recall having multiple windows open. I will see if journalctl has some logs and test another device next time I can repro. I have an Nvidia gpu but this happens on wayland using the integrated Intel igpu -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478419] New: Krita crashes immediately when trying to make a brush with the Random Pick filter, am able to adjust settings on other filters
https://bugs.kde.org/show_bug.cgi?id=478419 Bug ID: 478419 Summary: Krita crashes immediately when trying to make a brush with the Random Pick filter, am able to adjust settings on other filters Classification: Applications Product: krita Version: 5.2.2 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: crash Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: gabrielle.l...@gmail.com Target Milestone: --- 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. Opened brush editor 2. Create new brush preset with filter engine 3. Select "Random Pick" Filter 4. Attempt to change settings by clicking on one of the sliders OBSERVED RESULT App crashes EXPECTED RESULT able to change settings without app crashing SOFTWARE/OS VERSIONS Windows: macOS: monterey 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.
[kwin] [Bug 478374] Click sometimes doesn't work in some apps
https://bugs.kde.org/show_bug.cgi?id=478374 --- Comment #2 from Paragoumba --- (In reply to Nate Graham from comment #1) > You also reported Bug 478400, which makes me suspect you may have a hardware > issue. Can you try another pointing device to rule that out? It happens both bugs happened multiple times with a touchpad and a mouse. I will try to reproduce with more devices -- You are receiving this mail because: You are watching all bug changes.
[yakuake] [Bug 373428] Separator for split terminals not visible unless the background is black
https://bugs.kde.org/show_bug.cgi?id=373428 jacob.brumm...@gmail.com changed: What|Removed |Added CC||jacob.brumm...@gmail.com --- Comment #2 from jacob.brumm...@gmail.com --- +1! I find the line very difficult to see especially once the screens are filled with text. Having the line be configurable (size/colour) would really help the legibility. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478331] Kwin performance tanks in gpu bound scenarios
https://bugs.kde.org/show_bug.cgi?id=478331 Nate Graham changed: What|Removed |Added CC||n...@kde.org, ||vlad.zahorod...@kde.org, ||xaver.h...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478290] enlarged cursor pixelated and blurry
https://bugs.kde.org/show_bug.cgi?id=478290 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |NOT A BUG --- Comment #1 from Nate Graham --- Yep, that's what happens when you take a pixmap image and enlarge it to many times its size :) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478297] GTK4 apps have no closing animation
https://bugs.kde.org/show_bug.cgi?id=478297 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #1 from Nate Graham --- Can reproduce. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 478351] DiscoverNotifier spams crash notifications on session opening
https://bugs.kde.org/show_bug.cgi?id=478351 --- Comment #4 from Paragoumba --- (In reply to Nate Graham from comment #3) > We're crashing here: > > > else if (QNetworkInformation::instance()->reachability() != > > QNetworkInformation::Reachability::Online) > > Can you comment on the network state your system was in when you experienced > this problem, as well as how you've configured networking on your machine? > Anything unusual? For example are you not using NetworkManager or have you > disabled or masked any of its system units? Etc. I am using NetworkManager with no particular configuration. I mainly had this problem when connected via WiFi and when having no access to the internet. It happened one time after I killed my session with magic SysRq (AltGr+PrnScr+R then E then I) which also killed NM and logging right after. It also happens when I connect to public Wifi with a captive portal before I log in and thus have no internet connection -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478312] Windows flipping upside down and thus becoming unclickable
https://bugs.kde.org/show_bug.cgi?id=478312 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 477103 *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477103] Window becomes huge and upside-down when its window title is long
https://bugs.kde.org/show_bug.cgi?id=477103 Nate Graham changed: What|Removed |Added CC||n...@d3sox.me --- Comment #6 from Nate Graham --- *** Bug 478312 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477103] Window becomes huge and upside-down when its window title is long
https://bugs.kde.org/show_bug.cgi?id=477103 Nate Graham changed: What|Removed |Added Severity|minor |normal Summary|Unexpected effect when the |Window becomes huge and |window title is long|upside-down when its window ||title is long -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478387] VLC window contects are blank
https://bugs.kde.org/show_bug.cgi?id=478387 --- Comment #2 from Doug --- (In reply to Nate Graham from comment #1) > Are you using X11 or Wayland? > > Do the window contents appear if you resize the window? I am using Wayland. The problem does not exist on X11. Resizing the windows does not make the window contents appear. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478311] When dragging window using touchscreen with Wobbly Windows effect enabled, window wobbling focal point is equal to where the pointer was, not where the finger is
https://bugs.kde.org/show_bug.cgi?id=478311 Nate Graham changed: What|Removed |Added CC||n...@kde.org Severity|normal |minor Keywords|qt6 | Summary|The Wobbly Windows effect |When dragging window using |wrongly thinks the window |touchscreen with Wobbly |was dragged by mouse, when |Windows effect enabled, |it is actually dragged by |window wobbling focal point |touch |is equal to where the ||pointer was, not where the ||finger is Component|Gestures|effects-various Version|5.90.0 |5.27.9 --- Comment #3 from Nate Graham --- Can reproduce. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 475632] When booting up with laptop lid closed, external monitor turns off after logging in and then session locks
https://bugs.kde.org/show_bug.cgi?id=475632 Nate Graham changed: What|Removed |Added CC||techxga...@outlook.com --- Comment #13 from Nate Graham --- *** Bug 478325 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478325] On a docked laptop, Wayland session has a "black screen"
https://bugs.kde.org/show_bug.cgi?id=478325 Nate Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||n...@kde.org --- Comment #1 from Nate Graham --- *** This bug has been marked as a duplicate of bug 475632 *** -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 478351] DiscoverNotifier spams crash notifications on session opening
https://bugs.kde.org/show_bug.cgi?id=478351 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #3 from Nate Graham --- We're crashing here: > else if (QNetworkInformation::instance()->reachability() != > QNetworkInformation::Reachability::Online) Can you comment on the network state your system was in when you experienced this problem, as well as how you've configured networking on your machine? Anything unusual? For example are you not using NetworkManager or have you disabled or masked any of its system units? Etc. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 478418] New: Clicking with a pixel brush in some places doesn't work
https://bugs.kde.org/show_bug.cgi?id=478418 Bug ID: 478418 Summary: Clicking with a pixel brush in some places doesn't work Classification: Applications Product: krita Version: 5.2.2 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Brush engines Assignee: krita-bugs-n...@kde.org Reporter: garuda1...@proton.me Target Milestone: --- Created attachment 164098 --> https://bugs.kde.org/attachment.cgi?id=164098=edit Pixel brush don't works SUMMARY Hello. After update to Krita 5.2 the pixel brush with size 1 sometimes doesn't work in certain positions. These positions are between the pixels that the pixel grid shows. I've linked an image to show where it is. STEPS TO REPRODUCE 1. Choose the pixel brush with size 1 2. Enable the pixel grid 3. Try using the brush between 4 pixel grid as in the image I attached OBSERVED RESULT Nothing happens. Brush doesn't work if you don't drag EXPECTED RESULT Brush make a pixel. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Linux Mint 21.2 XFCE ADDITIONAL INFORMATION This bug happens with 5.2+. I don't know about Nightly Builds because I can't download it (it looks like the pages are down). This bug does not occur in version 5.15. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 478351] DiscoverNotifier spams crash notifications on session opening
https://bugs.kde.org/show_bug.cgi?id=478351
Nate Graham changed:
What|Removed |Added
CC||n...@kde.org
Severity|normal |crash
--- Comment #2 from Nate Graham ---
Application: DiscoverNotifier (DiscoverNotifier), signal: Segmentation fault
Content of s_kcrashErrorMessage: std::unique_ptr = {get() = }
[KCrash Handler]
#6 std::__uniq_ptr_impl >::_M_ptr() const
(this=) at
/usr/src/debug/qt6-base/build/include/QtNetwork/6.6.1/QtNetwork/private/../../../../../../qtbase-everywhere-src-6.6.1/src/network/kernel/qnetworkinformation_p.h:51
#7 std::unique_ptr >::get() const (this=) at /usr/include/c++/13.2.1/bits/unique_ptr.h:470
#8 std::unique_ptr >::operator->() const
(this=) at /usr/include/c++/13.2.1/bits/unique_ptr.h:463
#9 QNetworkInformation::reachability() const (this=0x0) at
/usr/src/debug/qt6-base/qtbase-everywhere-src-6.6.1/src/network/kernel/qnetworkinformation.cpp:518
#10 0x555fc2cb59dd in DiscoverNotifier::state() const (this=0x7ffcff8775c8)
at /usr/src/debug/discover/discover-5.90.0/notifier/DiscoverNotifier.cpp:212
#11 DiscoverNotifier::notifyAboutUpdates() const
(this=this@entry=0x7ffcff8775c8) at
/usr/src/debug/discover/discover-5.90.0/notifier/DiscoverNotifier.cpp:100
#12 0x555fc2cbb15a in DiscoverNotifier::refreshUnattended()
(this=0x7ffcff8775c8) at
/usr/src/debug/discover/discover-5.90.0/notifier/DiscoverNotifier.cpp:189
#13 DiscoverNotifier::DiscoverNotifier(QObject*) (this=0x7ffcff8775c8,
parent=0x0) at
/usr/src/debug/discover/discover-5.90.0/notifier/DiscoverNotifier.cpp:39
#14 0x555fc2cb33fb in NotifierItem::NotifierItem() (this=0x7ffcff8775b0) at
/usr/src/debug/discover/discover-5.90.0/notifier/NotifierItem.cpp:27
#15 main(int, char**) (argc=, argv=) at
/usr/src/debug/discover/discover-5.90.0/notifier/main.cpp:33
[Inferior 1 (process 2103) detached]
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 478400] Minimizing apps with the task manager sometimes doesn't work
https://bugs.kde.org/show_bug.cgi?id=478400 Nate Graham changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=478374 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478374] Click sometimes doesn't work in some apps
https://bugs.kde.org/show_bug.cgi?id=478374 Nate Graham changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||n...@kde.org See Also||https://bugs.kde.org/show_b ||ug.cgi?id=478400 --- Comment #1 from Nate Graham --- You also reported Bug 478400, which makes me suspect you may have a hardware issue. Can you try another pointing device to rule that out? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478387] VLC window contects are blank
https://bugs.kde.org/show_bug.cgi?id=478387 Nate Graham changed: What|Removed |Added CC||n...@kde.org Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Nate Graham --- Are you using X11 or Wayland? Do the window contents appear if you resize the window? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478321] Trackpad gesture to change desktops is too fast
https://bugs.kde.org/show_bug.cgi?id=478321 Nate Graham changed: What|Removed |Added Summary|Trackpad gesture to change |Trackpad gesture to change |desktops skips more than|desktops is too fast |one desktop | CC||n...@kde.org Severity|normal |minor Keywords|qt6 |usability -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478400] Minimizing apps with the task manager sometimes doesn't work
https://bugs.kde.org/show_bug.cgi?id=478400 Nate Graham changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC||n...@kde.org Status|REPORTED|NEEDSINFO --- Comment #1 from Nate Graham --- Does it *sometimes* not work, or *always* not work? Do the apps for which it doesn't work have multiple windows open? Can you run `journalctl -f` and see if something it printed there when you try to minimnize an app by clicking on it and it doesn't work? Can you plug in an external mouse (or a different mouse) to see if that helps? Do you have an NVIDIA GPU? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built
https://bugs.kde.org/show_bug.cgi?id=478416 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 478416] Crash on eMail sending since yesterdays git master snapshot built
https://bugs.kde.org/show_bug.cgi?id=478416 Bug Janitor Service changed: What|Removed |Added Severity|major |crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478413] Reconnecting a monitor causes the super key shortcut for application launcher to stop working
https://bugs.kde.org/show_bug.cgi?id=478413 Nate Graham changed: What|Removed |Added Product|kde |plasmashell Version|unspecified |master Assignee|unassigned-b...@kde.org |plasma-b...@kde.org Target Milestone|--- |1.0 Component|general |Panel Keywords||multiscreen CC||n...@kde.org, ||niccolo.venera...@gmail.com --- Comment #1 from Nate Graham --- Cannot reproduce when the panel containing Kickoff is on either the screen that gets unplugged and re-plugged, or the one that doesn't. In both cases, the Super key opens Kickoff after replugging the screen. If it's relevant, my hardware is all Intel (CPU and GPU), no AMD. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 477745] The scrolling speed slider needs an input spinbox
https://bugs.kde.org/show_bug.cgi?id=477745 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de Keywords|qt6 | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478379] Emoji selector freezing.
https://bugs.kde.org/show_bug.cgi?id=478379 Nate Graham changed: What|Removed |Added URL||https://bugreports.qt.io/br ||owse/QTBUG-120007 Resolution|--- |UPSTREAM CC||n...@kde.org Status|CONFIRMED |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 478348] Krunner crash, when starting
https://bugs.kde.org/show_bug.cgi?id=478348 Nate Graham changed: What|Removed |Added CC||n...@kde.org --- Comment #3 from Nate Graham --- Backtrace is all in Qt. I suspect a local DBus problem. -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 478285] Android phone not detected since updating to Plasma 6
https://bugs.kde.org/show_bug.cgi?id=478285 Nate Graham changed: What|Removed |Added CC||n...@kde.org, ||sit...@kde.org --- Comment #3 from Nate Graham --- Can also reproduce. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 478397] Recent files doesn't work
https://bugs.kde.org/show_bug.cgi?id=478397 Nate Graham changed: What|Removed |Added Severity|grave |major CC||me...@kde.org, n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462119] Empty menu in Panels and Desktops Management when there are no other screens
https://bugs.kde.org/show_bug.cgi?id=462119 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Severity|normal |minor Status|REPORTED|CONFIRMED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462119] Empty menu in Panels and Desktops Management when there are no other screens
https://bugs.kde.org/show_bug.cgi?id=462119 Nate Graham changed: What|Removed |Added Ever confirmed|1 |0 Status|RESOLVED|REPORTED Summary|Empty menu in Panels and|Empty menu in Panels and |Desktops Management |Desktops Management when ||there are no other screens Resolution|FIXED |--- Version Fixed In|6.0 | --- Comment #4 from Nate Graham --- Ahh you need to have no other screens--either active or inactive. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 478417] New: System Monitor doesn't display any CPU usage for most applications
https://bugs.kde.org/show_bug.cgi?id=478417 Bug ID: 478417 Summary: System Monitor doesn't display any CPU usage for most applications Classification: Applications Product: plasma-systemmonitor Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: ly...@bune.city CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- Created attachment 164097 --> https://bugs.kde.org/attachment.cgi?id=164097=edit Screenshot of the Applications tab showing that most processes have 0% CPU usage. SUMMARY Very few applications/processes in Plasma's System Monitor display any CPU usage at all. Htop is able to reliably display this information. STEPS TO REPRODUCE 1. Open System Monitor 2. Switch to Applications or Processes tab OBSERVED RESULT Most applications have a blank entry for CPU usage. EXPECTED RESULT Most applications have some level of CPU usage. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kernel 6.5.12-300.fc39.x86_64 (available in About System) KDE Plasma Version: 5.27.9 KDE Frameworks Version: 5.111.0 Qt Version: 5.15.11 ADDITIONAL INFORMATION Screenshots of System Monitor (and htop for comparison) are provided here: https://imgur.com/a/VFwN209 -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 477802] XWayland windows do not appear in Wayland session in KDE Neon Unstable
https://bugs.kde.org/show_bug.cgi?id=477802 Nate Graham changed: What|Removed |Added Product|kwin|neon Assignee|kwin-bugs-n...@kde.org |neon-b...@kde.org CC||j...@jriddell.org, ||neon-b...@kde.org, ||sit...@kde.org Version|5.90.0 |unspecified Component|wayland-generic |Packages Unstable Edition -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 478249] Discover/No preview
https://bugs.kde.org/show_bug.cgi?id=478249 --- Comment #3 from Nate Graham --- I'm afraid we still need more information that that. Please read the wiki article I provided to learn how to report an actionable bug. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 473849] Invitations shown as plain text and not ask for import
https://bugs.kde.org/show_bug.cgi?id=473849 Robby Engelmann changed: What|Removed |Added Resolution|--- |WORKSFORME CC||robby.engelmann@r-engelmann ||.de Status|REPORTED|RESOLVED --- Comment #1 from Robby Engelmann --- seem to work again after switched to qt6 builds -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478202] Interface one minute lag while saving "data:image..." from Vivaldi (Chromium)
https://bugs.kde.org/show_bug.cgi?id=478202 Nate Graham changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 478416] New: Crash on eMail sending since yesterdays git master snapshot built
https://bugs.kde.org/show_bug.cgi?id=478416 Bug ID: 478416 Summary: Crash on eMail sending since yesterdays git master snapshot built Classification: Applications Product: kmail2 Version: Git (master) Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: kdepim-b...@kde.org Reporter: robby.engelm...@r-engelmann.de Target Milestone: --- SUMMARY Since yesterdays git master snapshot of the qt6 megarelease as being provided by openSUSE, Email sending does not work anymore SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20231210 KDE Plasma Version: 5.90.90 KDE Frameworks Version: 5.247.0 Qt Version: 6.6.1 Kernel Version: 6.6.3-1-default (64-bit) Graphics Platform: Wayland Processors: 20 × 13th Gen Intel® Core™ i7-13700H Memory: 62.5 GiB of RAM Graphics Processor: Mesa Intel® Graphics Manufacturer: TUXEDO Product Name: TUXEDO InfinityBook Pro Gen8 (MK1) -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 478415] New: Sound alarm through all speakers
https://bugs.kde.org/show_bug.cgi?id=478415 Bug ID: 478415 Summary: Sound alarm through all speakers Classification: Applications Product: KClock Version: 23.08.4 Platform: postmarketOS OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: espi...@gmail.com Reporter: julia...@posteo.de CC: hanyo...@protonmail.com Target Milestone: --- SUMMARY When using a device with multiple speakers, such as the xiaomi-wt88047 phone, the alarm will ring from the back speaker. If you have such a device laying with the back on something soft, such as your mattress, the alarm might become completely inaudible. STEPS TO REPRODUCE 1. Set alarm 2. Set device speaker side down on a mattress 3. Alarm is inaudible when it rings OBSERVED RESULT The alarm only rings through the main speaker. EXPECTED RESULT The alarm should also ring through the secondary speaker, to improve the chances of it being heard. ADDITIONAL INFORMATION Other dealings with the audio system have been discussed here: https://bugs.kde.org/show_bug.cgi?id=471064 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 478165] The hovered clipboard item is blurry with scale factor of 150% or less
https://bugs.kde.org/show_bug.cgi?id=478165 Nate Graham changed: What|Removed |Added Latest Commit||https://invent.kde.org/plas ||ma/plasma-workspace/-/commi ||t/a4b809b345ae7bf6c63fe16da ||b41d9bf506a6965 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Nate Graham --- Git commit a4b809b345ae7bf6c63fe16dab41d9bf506a6965 by Nate Graham. Committed on 11/12/2023 at 23:01. Pushed by ngraham into branch 'master'. applets/clipboard: round up divided GridUnits Otherwise the value can be non-deterministic and cause blurriness. M +3-3applets/clipboard/contents/ui/ClipboardItemDelegate.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/a4b809b345ae7bf6c63fe16dab41d9bf506a6965 -- You are receiving this mail because: You are watching all bug changes.
[Haruna] [Bug 456482] hardware decoding doesn't work
https://bugs.kde.org/show_bug.cgi?id=456482 --- Comment #19 from sunsp...@gmail.com --- The Haruna flatpak can be launched with vaapi decoding from the terminal with: "QT_XCB_GL_INTEGRATION="xcb_egl" org.kde.haruna" Now the next challenge is figuring out how to edit the GUI so that the terminal isn't needed. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 478269] kwin_wayland crash when creating a folder with Dolphin with the filename dialog popping up
https://bugs.kde.org/show_bug.cgi?id=478269 Zamundaaa changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/kwin/-/commit/d228dc173a |ma/kwin/-/commit/0d59f48fbf |24bc27a895d4924936a1d91d7c2 |2cbbcc71556f0ce005d939c604f |5b9 |2c4 --- Comment #4 from Zamundaaa --- Git commit 0d59f48fbf2cbbcc71556f0ce005d939c604f2c4 by Xaver Hugl. Committed on 11/12/2023 at 22:43. Pushed by zamundaaa into branch 'Plasma/5.27'. xdgshellwindow: make maxSize always >= minSize by enforcing the same minimum (cherry picked from commit d228dc173a24bc27a895d4924936a1d91d7c25b9) M +4-2src/xdgshellwindow.cpp https://invent.kde.org/plasma/kwin/-/commit/0d59f48fbf2cbbcc71556f0ce005d939c604f2c4 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443148] Invert screen colors action doesn't work on Wayland with an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=443148 Zamundaaa changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/plas ||ma/kwin/-/commit/6f06bf1989 ||3bcf70b7dfa4b85c8529a2d2abd ||f1a Status|ASSIGNED|RESOLVED --- Comment #13 from Zamundaaa --- Git commit 6f06bf19893bcf70b7dfa4b85c8529a2d2abdf1a by Xaver Hugl. Committed on 11/12/2023 at 22:46. Pushed by vladz into branch 'master'. plugins/invert: support color management To do this, this commit adds infrastructure to include glsl files, extracts all the color management functions and uniforms into such a file, and makes use of it in the invert effect A +108 -0src/opengl/colormanagement.glsl M +80 -114 src/opengl/glshadermanager.cpp M +1-0src/opengl/glshadermanager.h A +9-0src/opengl/saturation.glsl M +10 -8src/plugins/invert/shaders/invert.frag M +11 -8src/plugins/invert/shaders/invert_core.frag M +3-1src/resources.qrc https://invent.kde.org/plasma/kwin/-/commit/6f06bf19893bcf70b7dfa4b85c8529a2d2abdf1a -- You are receiving this mail because: You are watching all bug changes.
[KClock] [Bug 465346] Let the user dismiss/snooze alarms without unlocking
https://bugs.kde.org/show_bug.cgi?id=465346 Julian Groß changed: What|Removed |Added CC||julia...@posteo.de -- You are receiving this mail because: You are watching all bug changes.
