[www.kde.org] [Bug 467556] New: [jp.kde.org] JKUG website displays wrong kanji variants
https://bugs.kde.org/show_bug.cgi?id=467556 Bug ID: 467556 Summary: [jp.kde.org] JKUG website displays wrong kanji variants Classification: Websites Product: www.kde.org Version: unspecified Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kde-...@kde.org Reporter: xnagyti...@gmail.com Target Milestone: --- SUMMARY The Japanese KDE Users' Group website at https://jp.kde.org/ doesn't properly specify its content language as Japanese. This leads to kanji characters falling back to their default variants, which is simplified Chinese in this case. All that needs fixing is the lang attribute on the root HTML element of the website: --> -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467555] New: "Update Playback range" will not . Plus i cant render the animation below 2147483647 frames...
https://bugs.kde.org/show_bug.cgi?id=467555 Bug ID: 467555 Summary: "Update Playback range" will not . Plus i cant render the animation below 2147483647 frames... Classification: Applications Product: krita Version: 5.1.5 Platform: Compiled Sources OS: All Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: willb...@hotmail.com Target Milestone: --- Created attachment 157409 --> https://bugs.kde.org/attachment.cgi?id=157409=edit Screenshot of bug. "Update Playback range" will not . Plus i cant render the animation below 2147483647 frames... here is a screenshot of my end. I appreciate the work you put in and letting the public use such a great software, Thank you! this was copy and pasted as requested: 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. 2. 3. OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 154804] Add option for alternative Drag behaviour
https://bugs.kde.org/show_bug.cgi?id=154804 --- Comment #57 from illumilore --- "Key modifiers and even alternate mouse buttons are for power users only." Is that why windows, the OS famous for catering to "power users", uses modifier keys? And if there's one thing kde historically always shies away from, it is choice and power! but seriously, there are better options out there than kde now, ones in which put user friendly design first rather than last. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465823] Brave Icons wrong & Webapp Icons Missing
https://bugs.kde.org/show_bug.cgi?id=465823 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 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.
[Tokodon] [Bug 465056] Tokodon crash when opening "conversation"
https://bugs.kde.org/show_bug.cgi?id=465056 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 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.
[systemsettings] [Bug 465931] kde setup crash
https://bugs.kde.org/show_bug.cgi?id=465931 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 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.
[valgrind] [Bug 446236] Issues with Valgrind 3.8.1 version, after compiler upgrade
https://bugs.kde.org/show_bug.cgi?id=446236 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #6 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.
[kwin] [Bug 465848] Window decorations are very grainy and the entire system is acting "zoomed in", ie all the window decorations are enlarged all the widows are enlarged, the docks are enlarged etc.
https://bugs.kde.org/show_bug.cgi?id=465848 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.
[systemsettings] [Bug 420866] Hotkeys including the ñ key doesn't work
https://bugs.kde.org/show_bug.cgi?id=420866 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #6 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.
[kate] [Bug 466531] Kate stops responding after pasting a very long line
https://bugs.kde.org/show_bug.cgi?id=466531 --- Comment #6 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 466193] Panel disappears after reboot since Frameworks 5.102.0 update
https://bugs.kde.org/show_bug.cgi?id=466193 --- Comment #8 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.
[neon] [Bug 467372] Today's update fails with unmet dependencies
https://bugs.kde.org/show_bug.cgi?id=467372 Jaime Antonio Gonzalez changed: What|Removed |Added CC||enigma1052...@gmail.com --- Comment #7 from Jaime Antonio Gonzalez --- I got a new round of updates on my main computer and now it deleted Lutris, at least it kept my games and preferences, so reinstalling Lutris did the trick. Looks like everything that is related to wine is suffering the side effects of whatever is going on. -- You are receiving this mail because: You are watching all bug changes.
[plasma-integration] [Bug 467553] workspace Behaviour - Screen Edges sudden stopped working
https://bugs.kde.org/show_bug.cgi?id=467553 Bug Janitor Service changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! However Plasma 5.18.8 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.18.8, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467547] Logging out of Plasma 5.27.3 on Wayland as the second user on the system resulted in a black screen
https://bugs.kde.org/show_bug.cgi?id=467547 --- Comment #1 from Matt Fagnani --- I reproduced the black screen problem when logging out as the second user in my Fedora 38 installation. loginctl in the VT showed that the second user's session was still active and there wasn't a sddm session. The problem might involve the second user's session not being properly stopped so that the sddm session never started. The errors I reported might have prevented the second user's session from stopping. xdg-desktop-portal-kde crashes when run by sddm happened as at https://bugzilla.redhat.com/show_bug.cgi?id=2129479 when I logged out as the first user and the black screen didn't happen. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 467554] New: When activating 4K resolution from Wayland with a bi-directional HDMI EDID emulator, the computer crashes
https://bugs.kde.org/show_bug.cgi?id=467554 Bug ID: 467554 Summary: When activating 4K resolution from Wayland with a bi-directional HDMI EDID emulator, the computer crashes Classification: Plasma Product: KScreen Version: 5.27.3 Platform: Manjaro OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: common Assignee: kscreen-bugs-n...@kde.org Reporter: rondo...@gmail.com Target Milestone: --- Created attachment 157408 --> https://bugs.kde.org/attachment.cgi?id=157408=edit Wayland display modes SUMMARY *** When activating 4K resolution from Wayland with a bi-directional HDMI EDID emulator, the computer crashes *** STEPS TO REPRODUCE 1. Connect a bi-directional HDMI EDID emulator to the computer's HDMI output and connect the monitor's HDMI cable to it (https://www.amazon.com/-/Passthrough-Generrtion-Eliminado-Adaptador-Thunderbolt/dp/B07YMTMMH5?th=1=en_US) 2. Activate 4K resolution (3840x2160) in KDE with Wayland OBSERVED RESULT 1. The screen goes completely black and does not return to the previous resolution after a few seconds even though the new resolution has not been accepted. 2. I open a new console by pressing Ctrl + F2 and from there it tries to return to the KDE session by pressing Ctrl + F1 in an attempt to refresh the HDMI signal, when doing this the computer freezes and the keyboard stops responding . The only solution is to restart the machine by pressing the power button. EXPECTED RESULT It should correctly enable 4K resolution, in version prior to KDE 5.27.3 this worked fine. SOFTWARE/OS VERSIONS Operating System: Manjaro Linux KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.3.0-1-MANJARO (64-bit) --> Tested also with kernel 6.2.7. Graphics Platform: Wayland Processors: 8 × AMD Ryzen 5 3550H with Radeon Vega Mobile Gfx Memory: 29,3 GiB of RAM Graphics Processor: AMD Radeon Vega 8 Graphics Manufacturer: BESSTAR TECH LIMITED Product Name: UM350 ADDITIONAL INFORMATION In 2K resolution everything works fine, but: - Although Wayland adequately detects all the resolutions offered by the HDMI EDID emulator (see attached screenshot. All resolutions have been tested from Windows and work correctly in this operating system), resolutions greater than 2K (2560x1440) cannot be activated properly, the screen goes black and after a few seconds it returns to the original resolution, which was 2K. - The only resolution greater than 2K that worked was 4K in previous versions of KDE, but now when switching to 4K the problem I mentioned above occurs and the computer ends up freezing. I've been looking at the logs, but I don't see anything, no error indication. Apparently Linux keeps running even though the screen goes black, until at 01:25:45 I am forced to press the power button because the keyboard is no longer responding: mar 19 01:01:01 ComputerM-K CROND[8701]: (root) CMD (run-parts /etc/cron.hourly) mar 19 01:01:01 ComputerM-K anacron[8708]: Anacron started on 2023-03-19 mar 19 01:01:01 ComputerM-K CROND[8700]: (root) CMDEND (run-parts /etc/cron.hourly) mar 19 01:01:01 ComputerM-K anacron[8708]: Normal exit (0 jobs run) mar 19 01:01:11 ComputerM-K NetworkManager[380]: [1679184071.3916] device (wlp2s0): set-hw-addr: set MAC address to 46:3B:11:6A:A9:3A (scanning) mar 19 01:02:36 ComputerM-K plasmashell[676]: QString::arg: 2 argument(s) missing in firefox mar 19 01:02:36 ComputerM-K systemd[527]: Started Firefox - Web Browser. mar 19 01:02:36 ComputerM-K plasmashell[676]: file:///usr/share/plasma/plasmoids/org.kde.plasma.taskmanager/contents/ui/Task.qml:286: Unable to assign [undefined] to QString mar 19 01:02:37 ComputerM-K plasmashell[8838]: ATTENTION: default value of option mesa_glthread overridden by environment. mar 19 01:02:37 ComputerM-K plasmashell[8838]: ATTENTION: default value of option mesa_glthread overridden by environment. mar 19 01:02:37 ComputerM-K plasmashell[8838]: ATTENTION: default value of option mesa_glthread overridden by environment. mar 19 01:02:37 ComputerM-K rtkit-daemon[603]: Supervising 10 threads of 3 processes of 1 users. mar 19 01:02:37 ComputerM-K rtkit-daemon[603]: Supervising 10 threads of 3 processes of 1 users. mar 19 01:02:37 ComputerM-K rtkit-daemon[603]: Supervising 10 threads of 3 processes of 1 users. mar 19 01:02:37 ComputerM-K rtkit-daemon[603]: Supervising 10 threads of 3 processes of 1 users. mar 19 01:02:37 ComputerM-K rtkit-daemon[603]: Supervising 10 threads of 3 processes of 1 users. mar 19 01:02:37 ComputerM-K rtkit-daemon[603]: Supervising 10 threads of 3 processes of 1 users. mar 19 01:02:37 ComputerM-K rtkit-daemon[603]: Successfully made thread 8978 of process 8838 owned by '1000' RT at priority 10. mar 19 01:02:37 ComputerM-K rtkit-daemon[603]: Supervising 11 threads of 4 processes of 1 users.
[Powerdevil] [Bug 467552] New: Powerdevil Crashes When Unlocking Screen After Powersaving
https://bugs.kde.org/show_bug.cgi?id=467552 Bug ID: 467552 Summary: Powerdevil Crashes When Unlocking Screen After Powersaving Classification: Plasma Product: Powerdevil Version: 5.27.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: carloslcas...@outlook.com CC: m...@ratijas.tk Target Milestone: --- Application: org_kde_powerdevil (5.27.2) Qt Version: 5.15.8 Frameworks Version: 5.103.0 Operating System: Linux 6.1.18-200.fc37.x86_64 x86_64 Windowing System: Wayland Distribution: Fedora Linux 37 (KDE Plasma) DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: Left computer for a period of time, and display went to sleep. Woke up screen and entered password to unlock, had unusual behavior of having to click unlock button after entering password, then when presented with desktop had crash notification for powerdevil The crash can be reproduced sometimes. -- Backtrace: Application: KDE Power Management System (org_kde_powerdevil), signal: Segmentation fault [KCrash Handler] #4 0x7f1d4fbd7ba7 in wl_proxy_marshal_array_flags () from /lib64/libwayland-client.so.0 #5 0x7f1d4fbd8219 in wl_proxy_marshal_flags () from /lib64/libwayland-client.so.0 #6 0x7f1d32c199c7 in DpmsManager::addScreen(QScreen*) () from /lib64/libKF5ScreenDpms.so.8 #7 0x7f1d32c1a390 in QtPrivate::QFunctorSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) () from /lib64/libKF5ScreenDpms.so.8 #8 0x7f1d550d0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #9 0x7f1d4fc60617 in QtWaylandClient::QWaylandDisplay::addRegistryListener(void (*)(void*, wl_registry*, unsigned int, QString const&, unsigned int), void*) () from /lib64/libQt5WaylandClient.so.5 #10 0x7f1d4fc7da2e in QWaylandClientExtension::addRegistryListener() () from /lib64/libQt5WaylandClient.so.5 #11 0x7f1d550abcda in QMetaMethod::invoke(QObject*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) const () from /lib64/libQt5Core.so.5 #12 0x7f1d550ace1e in QMetaObject::invokeMethod(QObject*, char const*, Qt::ConnectionType, QGenericReturnArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument, QGenericArgument) () from /lib64/libQt5Core.so.5 #13 0x7f1d32c1980b in WaylandDpmsHelper::blockUntilSupported() () from /lib64/libKF5ScreenDpms.so.8 #14 0x7f1d32c1b318 in KScreen::Dpms::isSupported() const () from /lib64/libKF5ScreenDpms.so.8 #15 0x7f1d55d9d36f in PowerDevil::ActionPool::init(PowerDevil::Core*) () from /lib64/libpowerdevilcore.so.2 #16 0x7f1d55da4ded in PowerDevil::Core::onBackendReady() () from /lib64/libpowerdevilcore.so.2 #17 0x7f1d550d0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #18 0x7f1d40152afa in PowerDevilUPowerBackend::initWithBrightness(bool) () from /usr/lib64/qt5/plugins/kf5/powerdevil/powerdevilupowerbackend.so #19 0x7f1d550d0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #20 0x7f1d40149f53 in PowerDevilUPowerBackend::brightnessSupportQueried(bool) () from /usr/lib64/qt5/plugins/kf5/powerdevil/powerdevilupowerbackend.so #21 0x7f1d550d0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #22 0x7f1d55c1c3d9 in KJob::result(KJob*, KJob::QPrivateSignal) () from /lib64/libKF5CoreAddons.so.5 #23 0x7f1d55c21e3b in KJob::finishJob(bool) () from /lib64/libKF5CoreAddons.so.5 #24 0x7f1d550d0e96 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #25 0x7f1d40be4863 in KAuth::DBusHelperProxy::qt_static_metacall(QObject*, QMetaObject::Call, int, void**) [clone .part.0] () from /usr/lib64/qt5/plugins/kauth/helper/kauth_helper_plugin.so #26 0x7f1d40be4f41 in KAuth::DBusHelperProxy::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/qt5/plugins/kauth/helper/kauth_helper_plugin.so #27 0x7f1d55b500bb in QDBusConnectionPrivate::deliverCall(QObject*, int, QDBusMessage const&, QVector const&, int) () from /lib64/libQt5DBus.so.5 #28 0x7f1d550c8134 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #29 0x7f1d5509d4e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #30 0x7f1d550a0854 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #31 0x7f1d550eeb07 in postEventSourceDispatch(_GSource*, int (*)(void*), void*) ()
[kwin] [Bug 467507] plasma-mobile fails to start on PP after kwin's commit eef9bd5c with "libkwinglutils: Shaders are not supported"
https://bugs.kde.org/show_bug.cgi?id=467507 Zamundaaa changed: What|Removed |Added CC||xaver.h...@gmail.com Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Zamundaaa --- This is fixed in 5.27.3 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467540] View -> Continuous (Off) does not prevent Mouse Scroll or Up/Down to go to next page
https://bugs.kde.org/show_bug.cgi?id=467540 --- Comment #1 from xpressra...@gmail.com --- To give more context. Think, when reading a multi-column magazine, you don't want to go past the current page with the same key you use to scroll within the page. Only one thing seems to work (somewhat). When you select single page, you can drag within the page with mouse or drag the scrollbar on the right with mouse. And use the mouse scrollbar to go to next page. However, I think there should be similar feature with just keyboard. Where you can use some key to move around a single page, and some other key to go to next page. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 467551] New: changing speed only affects the video & audio clips, not the titles, which incorrectly stay at their place in the timeline
https://bugs.kde.org/show_bug.cgi?id=467551 Bug ID: 467551 Summary: changing speed only affects the video & audio clips, not the titles, which incorrectly stay at their place in the timeline Classification: Applications Product: kdenlive Version: 22.12.2 Platform: Other OS: FreeBSD Status: REPORTED Severity: normal Priority: NOR Component: Effects & Transitions Assignee: j...@kdenlive.org Reporter: bugskde-...@fasterix.frmug.org Target Milestone: --- Created attachment 157407 --> https://bugs.kde.org/attachment.cgi?id=157407=edit Timeline screenshot: original grouped clip (left), duplicated grouped clip with speed changed to 25 % (right) SUMMARY Changing the speed of a clip only works on the video and audio, not the title(s), causing titles to stay at their original place. STEPS TO REPRODUCE 1. add a video + audio clip in the timeline 2. add title(s) clip(s) on a video track above 3. group everything 4. select everything 5. right click on one of the pieces and select "change speed" 6. set speed to 25% OBSERVED RESULT Only the right-clicked clip has its speed changed, all of the rest stays in place, which means the titles are not at the right place anymore. EXPECTED RESULT Titles follow the speed change, staying at their correct relative position. SOFTWARE/OS VERSIONS FreeBSD 13.1 KDE 5.101.1 Qt Version 5.15.7 Kdenlive 22.12.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 467544] QQmlApplicationEngine failed to load component in 18.03.2023 nightly
https://bugs.kde.org/show_bug.cgi?id=467544 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #2 from Nicolas Fella --- Should be fixed in the next nightly -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 467544] QQmlApplicationEngine failed to load component in 18.03.2023 nightly
https://bugs.kde.org/show_bug.cgi?id=467544 Nicolas Fella changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||https://invent.kde.org/pack ||aging/craft-blueprints-kde/ ||commit/f61b728a9be0428ec703 ||9ebffa3f1270f36bd86d Resolution|--- |FIXED --- Comment #1 from Nicolas Fella --- Git commit f61b728a9be0428ec7039ebffa3f1270f36bd86d by Nicolas Fella. Committed on 18/03/2023 at 23:21. Pushed by nicolasfella into branch 'master'. neochat: Add kquickcharts dep M +1-0kde/plasma-mobile/neochat/neochat.py https://invent.kde.org/packaging/craft-blueprints-kde/commit/f61b728a9be0428ec7039ebffa3f1270f36bd86d -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467550] New: baloo does not exclude folders under an excluded folder
https://bugs.kde.org/show_bug.cgi?id=467550 Bug ID: 467550 Summary: baloo does not exclude folders under an excluded folder Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: aar...@doofus.org Target Milestone: --- Created attachment 157406 --> https://bugs.kde.org/attachment.cgi?id=157406=edit File containing folders to be excluded 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 a large software package, i.e. Qt. 2. Start baloo 3. In a window run balooctl monitor 4. Run the command 'balooctl config add excludeFilters /home/[user]/Qt 5. Watch baloo continue to index in that folder OBSERVED RESULT Baloo will continue to index files in the excluded folder, even after restarting baloo. The folder is included in baloofilerc exclude folders[$e]=$HOME/Qt/ EXPECTED RESULT I expect Baloo to exclude any folders in the excluded folder list SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: OpenSUSE 15.4/5.104.0 (available in About System) KDE Plasma Version: 21.8.29 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 ADDITIONAL INFORMATION I have some very large trees that should be excluded from Baloo indexing in part due to the sheer size, i.e. Qt source code, but this appears to be broken. For example, I want to exclude /home/username/Qt and all folders underneath it, however even though this folder is in the exclude list, Baloo happily continues to index this. I have well over 1,000,000 files in the excluded trees and this is consuming a significant amount of processing, memory, and disk space to index. Another bug claims that this is the expected behavior, which IMO is completely broken. There must be a way to be able to exclude large trees of files from Baloo!!! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467549] New: When virtually dragging a titlebar's icon out of the window the cursor becomes a resize cursor
https://bugs.kde.org/show_bug.cgi?id=467549 Bug ID: 467549 Summary: When virtually dragging a titlebar's icon out of the window the cursor becomes a resize cursor Classification: Plasma Product: plasmashell Version: 5.27.3 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: pos...@posteo.eu CC: k...@davidedmundson.co.uk Target Milestone: 1.0 STEPS TO REPRODUCE 1. Open a window 2. Click and hold the the left mouse button eg on the "close" icon in the titlebar 3. Move the mouse, while holding the left mouse button down, outside of the window OBSERVED RESULT The cursor changes into a resize-cursor but that has no effect otherwise. Nothing is resized. EXPECTED RESULT The cursor stays normal and? the icon becomes deselected. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230312 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467548] New: A new ~/.gtkrc-2.0-kde4 file is always created
https://bugs.kde.org/show_bug.cgi?id=467548 Bug ID: 467548 Summary: A new ~/.gtkrc-2.0-kde4 file is always created Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_style Assignee: plasma-b...@kde.org Reporter: b...@brsvh.org CC: m...@gikari.com Target Milestone: --- SUMMARY I noticed that the gtk configuration file of version 5.27.2 follows the GTK environment variables better, but my home directory still generates the file .gtkrc-2.0-kde4 after every login. This file looks like it belongs to KDE4 from the naming, has it been deprecated? STEPS TO REPRODUCE 1. Delete ~/.gtkrc-2.0-kde4 2. Logout and re-login OBSERVED RESULT This file is always created or . EXPECTED RESULT It no longer create. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467547] New: Logging out of Plasma 5.27.3 on Wayland as the second user on the system resulted in a black screen
https://bugs.kde.org/show_bug.cgi?id=467547 Bug ID: 467547 Summary: Logging out of Plasma 5.27.3 on Wayland as the second user on the system resulted in a black screen Classification: Plasma Product: kwin Version: 5.27.3 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 157405 --> https://bugs.kde.org/attachment.cgi?id=157405=edit Journal for boot of Fedora-KDE-Live-x86_64-38-20230318.n.0.iso in a QEMU/KVM VM in GNOME Boxes in which the black screen happened 3 times SUMMARY I'm using a Fedora 38 KDE Plasma installation with two users. I logged in to Plasma 5.27.3 on Wayland as the second user, and then I logged out of Plasma. The system just showed a black screen with a blinking text cursor at the top-left of the screen. I switched to another VT and logged in. systemctl status sddm showed that sddm was running while the black screen happened. I ran sudo systemctl restart sddm which showed sddm on Wayland with the kwin_wayland compositor. This problem didn't happen when I logged in as the first user and logged out. I reproduced this problem using Fedora-KDE-Live-x86_64-38-20230318.n.0.iso in a QEMU/KVM VM in GNOME Boxes. I created a second user in System Settings in Plasma 5.27.3 on Wayland. I logged out and logged in as the second user. I logged out as the second user. The journal showed that dbus-:1.2-org.kde.LogoutPrompt@0.service failed and kwin_wayland_wrapper had an error (EE) failed to read Wayland events: Broken pipe. Various KDE programs had errors like The Wayland connection broke. Did the Wayland compositor die? kwin_wayland might've stopped before the other KDE programs leading to those errors. Mar 18 17:46:48 systemd[2832]: Started dbus-:1.2-org.kde.LogoutPrompt@0.service. Mar 18 17:46:49 ksmserver-logout-greeter[4260]: libEGL warning: egl: failed to create dri2 screen Mar 18 17:46:49 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mar 18 17:46:49 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mar 18 17:46:49 kernel: Lockdown: systemd-logind: hibernation is restricted; see man kernel_lockdown.7 Mar 18 17:46:49 ksmserver-logout-greeter[4260]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Mar 18 17:46:49 ksmserver-logout-greeter[4260]: qt.qpa.wayland: Wayland does not support QWindow::requestActivate() Mar 18 17:46:51 systemd[2832]: Started dbus-:1.2-org.kde.Shutdown@0.service. Mar 18 17:46:51 systemd[2832]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Main process exited, code=exited, status=1/FAILURE Mar 18 17:46:51 systemd[2832]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Failed with result 'exit-code'. Mar 18 17:46:51 systemd[2832]: dbus-:1.2-org.kde.LogoutPrompt@0.service: Consumed 1.976s CPU time. Mar 18 17:46:52 kwin_wayland_wrapper[2982]: (EE) failed to read Wayland events: Broken pipe Mar 18 17:46:52 kded5[3076]: X connection to :0 broken (explicit kill or server shutdown). Mar 18 17:46:52 kaccess[3353]: The X11 connection broke (error 1). Did the X11 server die? Mar 18 17:46:52 systemd[2832]: app-kaccess@autostart.service: Main process exited, code=exited, status=1/FAILURE Mar 18 17:46:52 systemd[2832]: app-kaccess@autostart.service: Failed with result 'exit-code'. Mar 18 17:46:52 kwin_wayland[2910]: QtDBus: cannot relay signals from parent QObject(0x561525cd4740 "") unless they are emitted in the object's thread QThread(0x561525bd5cb8 "libinput-connection"). Current thread is QThread(0x561525b95790 ""). Mar 18 17:46:52 imsettings-daemon[3367]: [52.190749]: IMSettings-Daemon[3367]: INFO: Stopped main process for IBus with the status 0 [pid: 3647] Mar 18 17:46:52 kwalletd5[2855]: The Wayland connection broke. Did the Wayland compositor die? Mar 18 17:46:52 kded5[3004]: The Wayland connection broke. Did the Wayland compositor die? Mar 18 17:46:52 kactivitymanagerd[3036]: The Wayland connection broke. Did the Wayland compositor die? Mar 18 17:46:52 DiscoverNotifier[3355]: The Wayland connection broke. Did the Wayland compositor die? Mar 18 17:46:52 akonadi_control[3646]: The Wayland connection broke. Did the Wayland compositor die? Mar 18 17:46:52 kded5[3004]: The Wayland connection broke. Did the Wayland compositor die? Mar 18 17:46:52 polkit-kde-authentication-agent-1[3096]: The Wayland connection broke. Did the Wayland compositor die? Mar 18 17:46:52 kdeconnectd[3341]: The Wayland connection broke. Did the Wayland compositor die? Mar 18 17:46:52 xdg-desktop-por[3171]: Lost connection to Wayland compositor. Mar 18 17:46:52 xdg-desktop-portal-kde[3099]: The Wayland connection broke. Did the Wayland compositor die? Mar 18 17:4
[kpat] [Bug 439420] crash when switching games
https://bugs.kde.org/show_bug.cgi?id=439420 --- Comment #9 from Brian Kaye --- Tried the attached game several times. No crash or quit after selecting klondik any of those times. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 416501] Compositing prevents laptop to wake up from sleep state
https://bugs.kde.org/show_bug.cgi?id=416501 Andriy Kushnir changed: What|Removed |Added CC||m...@orhideous.name --- Comment #7 from Andriy Kushnir --- This bug started to occur for me in the last week or so. --- Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 5.19.0-35-generic (64-bit) Graphics Platform: Wayland Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor Memory: 62,7 GiB of RAM Graphics Processor: NVIDIA GeForce GTX 1070/PCIe/SSE2 Product Name: X570 Extreme4 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 467546] New: Brush cursors are a mess
https://bugs.kde.org/show_bug.cgi?id=467546 Bug ID: 467546 Summary: Brush cursors are a mess Classification: Applications Product: krita Version: 5.1.5 Platform: Neon OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Usability Assignee: krita-bugs-n...@kde.org Reporter: xnagyti...@gmail.com Target Milestone: --- Created attachment 157404 --> https://bugs.kde.org/attachment.cgi?id=157404=edit Toolbar icons vs. Tool cursors SUMMARY The brush cursors icons that Krita displays when using various tools on the canvas are kinda a mess right now. Would be nice having them cleaned up or redrawn. STEPS TO REPRODUCE 1. Set "Configure Krita..." -> "General" -> "Cursor" -> "Brush Cursor Icon" to "Tool Icon" 2. Select mentioned tools below and hover the canvas. ISSUES - Edit Shapes Tool: Uses a custom narrow cursor instead of the system cursor any other tool uses in similar cases. - Freehand Brush Tool, Polygon Tool, Crop Tool, Polygonal Selection Tool: Cursor uses obsolete icon from Krita 2.x - Dynamic Brush Tool, Multibrush Brush Tool, Colorize Mask Tool: Reuses the obsolete Freehand Brush cursor. - Freehand Selection Tool: The bean is much thicker on the cursor than the toolbar icon. Also no other custom cursor gives the pointer a tail. - Line Tool: The angle of the line is different between the cursor and the toolbar icon. - Ellipse Tool, Elliptical Selection Tool: Cursor is too oval compared to the toolbar icon. - Polyline Tool: Lines on the cursor intersect sooner than on the toolbar icon. - Smart Patch Tool: Missing cursor. - Fill Tool: Weird Windows 9x-style paint bucket cursor, very different from the current toolbar icon. - Sample Color Tool, Similar Color Selection Tool: Both of them use an eyedropper icon, however they are inconsistent with each other. The crosshair positions and eyedropper shapes are different. - Zoom Tool: The only cursor using 2px wide outlines. - Magnetic Curse Selection Tool: Magnet faces the opposite direction than on the toolbar icon. - Calligraphy Tool, Distance Measurement Tool: Both of them use a crosshair cursor, however they are inconsistent with each other. One of the uses a system cursor, the other one uses a custom bitmap. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.1 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 467541] 0.26.10: Test suite is failing
https://bugs.kde.org/show_bug.cgi?id=467541 --- Comment #3 from kloczek --- (In reply to Friedrich W. H. Kossebau from comment #1) [..] > In case the duplicated path separators are an issue here (bad in any case), > I pushed a commit to current 0.26 branch here: > https://invent.kde.org/utilities/okteta/-/commit/ > 67b3bb25b9fe8ce6794fa8038347a5adb4466478 > > Could you try again with that commit? Looks like that commit fixed fail of one unit + cd okteta-0.26.10 + xvfb-run -a /usr/bin/ctest --test-dir x86_64-redhat-linux-gnu --output-on-failure --force-new-ctest-process -j48 ' ' Internal ctest changing into directory: /home/tkloczko/rpmbuild/BUILD/okteta-0.26.10/x86_64-redhat-linux-gnu Test project /home/tkloczko/rpmbuild/BUILD/okteta-0.26.10/x86_64-redhat-linux-gnu Start 1: libkasten-core-testdocumenttest Start 2: libkasten-core-testdocumentfilesynchronizertest Start 3: libkasten-core-testdocumentfilesynchronizerfactorytest Start 4: libkasten-core-documentmanagertest Start 5: libpiecetable-piecetest Start 6: libpiecetable-piecetabletest Start 7: libpiecetable-testpiecetablechangetest Start 8: libpiecetable-testpiecetablechangeabstractpiecetablechangeiftest Start 9: libpiecetable-insertpiecetablechangeabstractpiecetablechangeiftest Start 10: libpiecetable-removepiecetablechangeabstractpiecetablechangeiftest Start 11: libpiecetable-replacepiecetablechangeabstractpiecetablechangeiftest Start 12: libpiecetable-swaprangespiecetablechangeabstractpiecetablechangeiftest Start 13: libpiecetable-grouppiecetablechangetest Start 14: libpiecetable-piecetablechangehistorytest Start 15: libpiecetable-revertablepiecetabletest Start 16: libokteta-core-arraychangemetricstest Start 17: libokteta-core-addressrangetest Start 18: libokteta-core-addressrangelisttest Start 19: libokteta-core-fixedsizebytearraymodeltest Start 20: libokteta-core-fixedsizebytearraymodelabstractbytearraymodeliftest Start 21: libokteta-core-bytearraymodeltest Start 22: libokteta-core-bytearraymodelabstractbytearraymodeliftest Start 23: libokteta-core-piecetablebytearraymodelabstractbytearraymodeliftest Start 24: libokteta-core-piecetablebytearraymodelversionableiftest Start 25: libokteta-core-valuecodectest Start 26: libokteta-core-charcodectest Start 27: libokteta-core-textcharcodectest Start 28: libokteta-core-textcharcodeccharcodeciftest Start 29: libokteta-core-ebcdic1047charcodeccharcodeciftest Start 30: libokteta-core-bookmarktest Start 31: libokteta-core-bookmarklisttest Start 32: libokteta-gui-selectiontest Start 33: libokteta-gui-coordtest Start 34: libokteta-gui-coordrangetest Start 35: libokteta-gui-coordrangelisttest Start 36: libokteta-gui-bytearraytablelayouttest Start 37: libokteta-gui-bytearraytablecursortest Start 38: oktetakasten-document-bytearraydocumenttest Start 39: oktetakasten-document-bytearraydocumentfactorytest Start 40: oktetakasten-io-bytearrayrawfilesynchronizertest Start 41: oktetakasten-io-bytearrayrawfilesynchronizerfactorytest Start 42: structures-primitivearraytest Start 43: structures-arraydatainformationtest Start 44: structures-basicdatainformationtest Start 45: structures-primitivedatainformationtest Start 46: structures-scriptclassestest Start 47: structures-uniondatainformationtest Start 48: structures-allprimitivetypestest 1/56 Test #1: libkasten-core-testdocumenttest .. Passed0.08 sec Start 49: structures-scriptvalueconvertertest 2/56 Test #2: libkasten-core-testdocumentfilesynchronizertest ..***Failed0.08 sec * Start testing of TestDocumentFileSynchronizerTest * Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.0.1 20230304 (Red Hat 13.0.1-0)), fedora 39 PASS : TestDocumentFileSynchronizerTest::initTestCase() PASS : TestDocumentFileSynchronizerTest::testLoadFromFile() FAIL! : TestDocumentFileSynchronizerTest::testLoadSaveFile() 'testDocument != nullptr' returned FALSE. () Loc: [/home/tkloczko/rpmbuild/BUILD/okteta-0.26.10/libs/kasten/core/tests/testdocumentfilesynchronizertest.cpp(80)] QWARN : TestDocumentFileSynchronizerTest::testLoadReloadFile() QIODevice::write (QFile, "/home/tkloczko/.kde-unit-test/testdocumentfile1synchronizertest/test1.data"): device not open FAIL! : TestDocumentFileSynchronizerTest::testLoadReloadFile() 'testDocument != nullptr' returned FALSE. () Loc: [/home/tkloczko/rpmbuild/BUILD/okteta-0.26.10/libs/kasten/core/tests/testdocumentfilesynchronizertest.cpp(164)] QWARN : TestDocumentFileSynchronizerTest::testChangeFile() QIODevice::write (QFile,
[okteta] [Bug 467541] 0.26.10: Test suite is failing
https://bugs.kde.org/show_bug.cgi?id=467541 --- Comment #2 from kloczek --- (In reply to Friedrich W. H. Kossebau from comment #1) [..] > What Qt version are you using? 5.15.8 > The following looks suspicious: > QWARN : TestDocumentFileSynchronizerTest::testLoadReloadFile() > QIODevice::write (QFile, > "/home/tkloczko//.kde-unit-test//testdocumentfile1synchronizertest//test1. > data"): device not open > > In case the duplicated path separators are an issue here (bad in any case), > I pushed a commit to current 0.26 branch here: > https://invent.kde.org/utilities/okteta/-/commit/ > 67b3bb25b9fe8ce6794fa8038347a5adb4466478 Will back shortly with result. > Could you try again with that commit? > > The other question would be: is home/tkloczko/.kde-unit-test/ writable > during your test runs? Yes it is writeable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446311] Kicked back tty right after login on Wayland
https://bugs.kde.org/show_bug.cgi?id=446311 Colin Gauvin changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467030] Some icons and icons states doesn't have color consistency with the rest of the window when titlebars accent-colored is used
https://bugs.kde.org/show_bug.cgi?id=467030 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 467251] When configuring Breeze Light to make titlebars accent colored, buttons on the colored titlebar don't have visible hover outlines
https://bugs.kde.org/show_bug.cgi?id=467251 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 466417] Menu Editor crashes when creating or modifying item
https://bugs.kde.org/show_bug.cgi?id=466417 --- Comment #1 from Colin Gauvin --- Still happening on 5.27.2. Can't edit any menu entries. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 446311] Kicked back tty right after login on Wayland
https://bugs.kde.org/show_bug.cgi?id=446311 --- Comment #10 from Colin Gauvin --- This has stopped happening. Not sure when because I was on X11 for a while, but on Plasma 5.27.2, Frameworks 5.104.0, Qt 5.15.8, Kernel 6.2.1-1-default (64 bit) Wayland, openSUSE Tumbleweed 20230316, this bug has vanished! Well done to whomever fixed it. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467215] macOS 11.74 Big Sur: digikam crashes unexpectedly after launching G'MIC
https://bugs.kde.org/show_bug.cgi?id=467215 --- Comment #10 from No_Planet_2 --- Thanks for the effort, which felt first brought a slight improvement, at least in the preview of the effects. Just updated digikam to version 8.0.0, but the crashes occur not only in the menu 'Colors' unchanged., also in Arrays and tiles etc.. Sometimes only when you apply the filter. Therefore I loaded the external data from G'MIC (about/download external data), unfortunately without effect. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 452628] Can not find a part of a word in a filename
https://bugs.kde.org/show_bug.cgi?id=452628 --- Comment #9 from tagwer...@innerjoin.org --- (In reply to Stefan Brüns from comment #8) > ... So dolphin should (optionally) crawl the filesystem (slow), > after having queried baloo (fast, allows metadata/content match) ... Talking ideal behaviours? I think probably so. Dolphin should know what baloo has indexed, rely on baloo's results where it can, fall back to its own search when it cannot. Something that can give a "seamless" search if you are in your home folder in Fedora. It would be quite a project -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 467545] New: KWin is not duck safe
https://bugs.kde.org/show_bug.cgi?id=467545 Bug ID: 467545 Summary: KWin is not duck safe Classification: Plasma Product: kwin Version: 5.27.3 Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: dan...@constexpr.org Target Milestone: --- Created attachment 157403 --> https://bugs.kde.org/attachment.cgi?id=157403=edit duck.webm SUMMARY KWin crashes when playing a specifically crafted video file using mpv ( https://mpv.io/ ). STEPS TO REPRODUCE 1. Play the attached video file with mpv -vo gpu (default) or -vo x11. Other players that show only the video without additional controls might work too but it is not guaranteed (e.g. mpv with -vo sdl does not reproduce the bug). OBSERVED RESULT KWin goes bye bye. EXPECTED RESULT KWin survives whatever window properties/dimensions mpv sets. SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.13 KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.1.7-gentoo (64-bit) Graphics Platform: X11 Processors: 64 × AMD Ryzen Threadripper 3970X 32-Core Processor Memory: 125.7 GiB of RAM Graphics Processor: AMD Radeon RX 6900 XT Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C59 System Version: 1.0 ADDITIONAL INFORMATION This is not a new bug in KWin, I have just been too lazy to report it. -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 466181] powerdevil crashes in KScreen::AbstractDpmsHelper::isSupported()
https://bugs.kde.org/show_bug.cgi?id=466181 mwc85.2...@gmail.com changed: What|Removed |Added CC||mwc85.2...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 467477] kup-purger doesn't work
https://bugs.kde.org/show_bug.cgi?id=467477 Simon Persson changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from Simon Persson --- Thanks for reporting! I fixed this problem in commit 96c0bc820 back in july 2021 but I have not found the time and motivation to release a new version of kup since. I will try. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 448833] Overlapping entries when filtering and deleting and filtering again several times
https://bugs.kde.org/show_bug.cgi?id=448833 Ricardo J. Barberis changed: What|Removed |Added CC||rica...@palmtx.com.ar -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 467544] New: QQmlApplicationEngine failed to load component in 18.03.2023 nightly
https://bugs.kde.org/show_bug.cgi?id=467544 Bug ID: 467544 Summary: QQmlApplicationEngine failed to load component in 18.03.2023 nightly Classification: Applications Product: NeoChat Version: unspecified Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: mic...@lebihan.pl CC: c...@carlschwan.eu Target Milestone: --- SUMMARY Hello, Today's nightly fails to start with: ``` PS C:\Users\Michel> &"C:\Program Files\NeoChat\bin\neochat.exe" PS C:\Users\Michel> kf.config.core: Use of KConfigWatcher without DBus support. You will not receive updates QQmlApplicationEngine failed to load component qrc:/main.qml:30:5: Type RoomPage unavailable qrc:/RoomPage.qml:573:13: Type ChatBox unavailable qrc:/ChatBox.qml:37:5: Type ChatBar unavailable qrc:/ChatBar.qml:351:17: Type PieProgressBar unavailable qrc:/PieProgressBar.qml:7:1: module "org.kde.quickcharts" is not installed ``` STEPS TO REPRODUCE 1. Install 18.03.2023 nightly 2. Try to launch it 3. Notice issue OBSERVED RESULT App won't launch EXPECTED RESULT App should launch SOFTWARE/OS VERSIONS Windows: Windows 11 Pro 22H2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467543] plasma crash
https://bugs.kde.org/show_bug.cgi?id=467543 Bug Janitor Service changed: What|Removed |Added Resolution|--- |DOWNSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Bug Janitor Service --- Thank you for the bug report! However Plasma 5.25.5 is no longer eligible for support or maintenance from KDE; supported versions are 5.27, and 5.27 or newer. Please upgrade to a supported version as soon as your distribution makes it available to you. Plasma is a fast-moving project, and bugs in one version are often fixed in the next one. If you need support for Plasma 5.25.5, please contact your distribution, who bears the responsibility of providing support for older releases that are no longer supported by KDE. If you can reproduce the issue after upgrading to a supported version, feel free to re-open this bug report. -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 467541] 0.26.10: Test suite is failing
https://bugs.kde.org/show_bug.cgi?id=467541 Friedrich W. H. Kossebau changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|NEEDSINFO --- Comment #1 from Friedrich W. H. Kossebau --- Thanks for the report. Cannot reproduce though, and has been passing for me locally (openSUSE TW) and on KDE CI all the time. See e.g. https://invent.kde.org/utilities/okteta/-/pipelines/302655/test_report for the last pipeline on the tag itself. What Qt version are you using? The following looks suspicious: QWARN : TestDocumentFileSynchronizerTest::testLoadReloadFile() QIODevice::write (QFile, "/home/tkloczko//.kde-unit-test//testdocumentfile1synchronizertest//test1.data"): device not open In case the duplicated path separators are an issue here (bad in any case), I pushed a commit to current 0.26 branch here: https://invent.kde.org/utilities/okteta/-/commit/67b3bb25b9fe8ce6794fa8038347a5adb4466478 Could you try again with that commit? The other question would be: is home/tkloczko/.kde-unit-test/ writable during your test runs? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467543] New: plasma crash
https://bugs.kde.org/show_bug.cgi?id=467543 Bug ID: 467543 Summary: plasma crash Classification: Plasma Product: plasmashell Version: 5.25.5 Platform: Compiled Sources OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: willscott1...@outlook.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Application: plasmashell (5.25.5) (Compiled from sources) Qt Version: 5.15.6 Frameworks Version: 5.98.0 Operating System: Linux 5.15.0-67-generic x86_64 Windowing System: X11 Distribution: Feren OS DrKonqi: 5.25.5 [KCrashBackend] -- Information about the crash: system was in lockscreen crash notification was there when i signed back in The reporter is unsure if this crash is reproducible. -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault [New LWP 3105] [New LWP 3248] [New LWP 3271] [New LWP 3272] [New LWP 3273] [New LWP 3274] [New LWP 3275] [New LWP 3276] [New LWP 3277] [New LWP ] [New LWP 3334] [New LWP 3369] [New LWP 3371] [New LWP 3372] [New LWP 3376] [New LWP 3377] [New LWP 3975] [New LWP 3976] [New LWP 3977] [New LWP 3978] [New LWP 3985] [New LWP 3986] [New LWP 3987] [New LWP 3988] [New LWP 3989] [New LWP 3990] [New LWP 3991] [New LWP 3992] [New LWP 3993] [New LWP 3994] [New LWP 4992] [New LWP 16564] [New LWP 16565] [New LWP 16797] [New LWP 18772] [New LWP 56664] [New LWP 56667] [New LWP 146933] [New LWP 146938] [New LWP 146942] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7fc182aaa73d in syscall () from /lib/x86_64-linux-gnu/libc.so.6 __preamble__ [Current thread is 1 (Thread 0x7fc17ebc32c0 (LWP 3087))] Thread 41 (Thread 0x7fc0d3fff700 (LWP 146942)): #0 0x7fc18266c376 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fc182e3a5eb in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7fc184ad7394 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #3 0x7fc184ad7809 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #4 0x7fc182e34543 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc182665609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #6 0x7fc182ab1133 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 40 (Thread 0x7fc0c758e700 (LWP 146938)): #0 0x7fc18266c376 in pthread_cond_wait@@GLIBC_2.3.2 () at /lib/x86_64-linux-gnu/libpthread.so.0 #1 0x7fc174d785eb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #2 0x7fc174d781eb in () at /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #3 0x7fc182665609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #4 0x7fc182ab1133 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 39 (Thread 0x7fc0caffe700 (LWP 146933)): [KCrash Handler] #4 0x7fc18344de4c in QImage::pixel(int, int) const () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #5 0x7fc1834501e6 in QImage::pixelColor(int, int) const () at /lib/x86_64-linux-gnu/libQt5Gui.so.5 #6 0x7fc1624c2ca0 in () at /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/libKirigamiPlugin.so #7 0x7fc1624ca5bb in () at /usr/lib/x86_64-linux-gnu/qt5/qml/org/kde/kirigami.2/libKirigamiPlugin.so #8 0x7fc182e37892 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fc182e34543 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fc182665609 in start_thread () at /lib/x86_64-linux-gnu/libpthread.so.0 #11 0x7fc182ab1133 in clone () at /lib/x86_64-linux-gnu/libc.so.6 Thread 38 (Thread 0x7fc0c89bc700 (LWP 56667)): #0 0x7ffc34495aed in clock_gettime () #1 0x7fc182a6f0b5 in clock_gettime () at /lib/x86_64-linux-gnu/libc.so.6 #2 0x7fc183075435 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #3 0x7fc183073ccd in QTimerInfoList::updateCurrentTime() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fc1830742a9 in QTimerInfoList::timerWait(timespec&) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7fc183075f2c in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7fc1811b78ef in g_main_context_prepare () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7fc1811b829b in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #8 0x7fc1811b84a3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #9 0x7fc183075b6b in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fc183019b0b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #11 0x7fc182e33342 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #12 0x7fc182e34543 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #13 0x7fc182665609 in start_thread () at
[okular] [Bug 467542] Font is distorted on Okular compared to MuPDF
https://bugs.kde.org/show_bug.cgi?id=467542 --- Comment #1 from medin --- Created attachment 157402 --> https://bugs.kde.org/attachment.cgi?id=157402=edit Test PDF file -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467542] New: Font is distorted on Okular compared to MuPDF
https://bugs.kde.org/show_bug.cgi?id=467542 Bug ID: 467542 Summary: Font is distorted on Okular compared to MuPDF Classification: Applications Product: okular Version: 22.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: med.medin.2...@gmail.com Target Milestone: --- Created attachment 157401 --> https://bugs.kde.org/attachment.cgi?id=157401=edit Font is distorted on Okular compared to MuPDF See attached image and pdf file for more info. -- You are receiving this mail because: You are watching all bug changes.
[plasma-mobile] [Bug 464466] background image and pinned applications dont survive reboot
https://bugs.kde.org/show_bug.cgi?id=464466 --- Comment #4 from Devin Lin --- This is incredibly strange that you're still having it, I don't experience this issue anymore since https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2601 was merged -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466299] Window previews for task manager icons showed the wrong colours when using the llvmpipe driver
https://bugs.kde.org/show_bug.cgi?id=466299 --- Comment #5 from Matt Fagnani --- Created attachment 157400 --> https://bugs.kde.org/attachment.cgi?id=157400=edit Recording with Plasma 5.27.3 on Wayland with wrong window preview colours in VM The window previews had different incorrect colours in Plasma 5.27.3 when using Fedora-KDE-Live-x86_64-38-20230318.n.0.iso in a QEMU/KVM VM in GNOME Boxes with 3D acceleration disabled using the llvmpipe mesa driver and the virtio_gpu kernel driver and in a Fedora 38 KDE Plasma installation with nomodeset on the kernel command line using llvmpipe and the simpledrm kernel driver. Window previews were orange where the programs were actually light blue and vice versa. Window previews had switched red and dark blue compared to the programs. Purple was shown in the previews where the programs were pink, and pink was shown in the previews where purple was shown in the programs. I'm attaching a recording showing this problem in Plasma 5.27.3 when using Fedora-KDE-Live-x86_64-38-20230318.n.0.iso in a QEMU/KVM VM in a Fedora 38 KDE Plasma installation. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 452628] Can not find a part of a word in a filename
https://bugs.kde.org/show_bug.cgi?id=452628 --- Comment #8 from Stefan Brüns --- (In reply to tagwerk19 from comment #7) > If you want baloo to find you "example" when you search for "xample", that's > a feature request 8-) > > However, in dolphin, that you get a different behavour searching dependent > on whether you have baloo enabled or not, or if you are searching from a > folder indexed or not indexed by baloo, that is confusing. But that is a bug in dolphin then. This bug has "frameworks-baloo" set as product. Even if baloo supported searching for something like "*.xample.*", it can not support searching for files not indexed. So dolphin should (optionally) crawl the filesystem (slow), after having queried baloo (fast, allows metadata/content match). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467510] Cannot open folder from "Apps" folder
https://bugs.kde.org/show_bug.cgi?id=467510 --- Comment #2 from mrbongo...@icloud.com --- I also forgot to add... [***@*** ~]$ dolphin org.kde.dolphin: could not find entry for charset= "Other encoding ()" kf.kio.workers.afc: Unhandled afc_error_t 32 kf.kio.core: "Internal Error\nPlease send a full bug report at https://bugs.kde.org\nUnhandled AFC error code '32'" kf.kio.workers.afc: Failed to get device info for free disk usage 2 kf.kio.workers.afc: Failed to get device info for free disk usage 2 kf.kio.workers.afc: Failed to get device info for free disk usage 2 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 458392] Fields to choose between password authentication and the other choice are too small to content French translation
https://bugs.kde.org/show_bug.cgi?id=458392 James Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED CC||james.h.graham@protonmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 467537] Labels in login screen are cropped
https://bugs.kde.org/show_bug.cgi?id=467537 James Graham changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE CC||james.h.graham@protonmail.c ||om --- Comment #1 from James Graham --- *** This bug has been marked as a duplicate of bug 458392 *** -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 458392] Fields to choose between password authentication and the other choice are too small to content French translation
https://bugs.kde.org/show_bug.cgi?id=458392 James Graham changed: What|Removed |Added CC||mic...@lebihan.pl --- Comment #1 from James Graham --- *** Bug 467537 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[okteta] [Bug 467541] New: 0.26.10: Test suite is failing
https://bugs.kde.org/show_bug.cgi?id=467541 Bug ID: 467541 Summary: 0.26.10: Test suite is failing Classification: Applications Product: okteta Version: 0.26.10 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kosse...@kde.org Reporter: kloczko.tom...@gmail.com Target Milestone: --- Looks like 0.26.10 test suitr is failing in two units + cd okteta-0.26.10 + xvfb-run -a /usr/bin/ctest --test-dir x86_64-redhat-linux-gnu --output-on-failure --force-new-ctest-process -j48 Internal ctest changing into directory: /home/tkloczko/rpmbuild/BUILD/okteta-0.26.10/x86_64-redhat-linux-gnu Test project /home/tkloczko/rpmbuild/BUILD/okteta-0.26.10/x86_64-redhat-linux-gnu Start 1: libkasten-core-testdocumenttest Start 2: libkasten-core-testdocumentfilesynchronizertest Start 3: libkasten-core-testdocumentfilesynchronizerfactorytest Start 4: libkasten-core-documentmanagertest Start 5: libpiecetable-piecetest Start 6: libpiecetable-piecetabletest Start 7: libpiecetable-testpiecetablechangetest Start 8: libpiecetable-testpiecetablechangeabstractpiecetablechangeiftest Start 9: libpiecetable-insertpiecetablechangeabstractpiecetablechangeiftest Start 10: libpiecetable-removepiecetablechangeabstractpiecetablechangeiftest Start 11: libpiecetable-replacepiecetablechangeabstractpiecetablechangeiftest Start 12: libpiecetable-swaprangespiecetablechangeabstractpiecetablechangeiftest Start 13: libpiecetable-grouppiecetablechangetest Start 14: libpiecetable-piecetablechangehistorytest Start 15: libpiecetable-revertablepiecetabletest Start 16: libokteta-core-arraychangemetricstest Start 17: libokteta-core-addressrangetest Start 18: libokteta-core-addressrangelisttest Start 19: libokteta-core-fixedsizebytearraymodeltest Start 20: libokteta-core-fixedsizebytearraymodelabstractbytearraymodeliftest Start 21: libokteta-core-bytearraymodeltest Start 22: libokteta-core-bytearraymodelabstractbytearraymodeliftest Start 23: libokteta-core-piecetablebytearraymodelabstractbytearraymodeliftest Start 24: libokteta-core-piecetablebytearraymodelversionableiftest Start 25: libokteta-core-valuecodectest Start 26: libokteta-core-charcodectest Start 27: libokteta-core-textcharcodectest Start 28: libokteta-core-textcharcodeccharcodeciftest Start 29: libokteta-core-ebcdic1047charcodeccharcodeciftest Start 30: libokteta-core-bookmarktest Start 31: libokteta-core-bookmarklisttest Start 32: libokteta-gui-selectiontest Start 33: libokteta-gui-coordtest Start 34: libokteta-gui-coordrangetest Start 35: libokteta-gui-coordrangelisttest Start 36: libokteta-gui-bytearraytablelayouttest Start 37: libokteta-gui-bytearraytablecursortest Start 38: oktetakasten-document-bytearraydocumenttest Start 39: oktetakasten-document-bytearraydocumentfactorytest Start 40: oktetakasten-io-bytearrayrawfilesynchronizertest Start 41: oktetakasten-io-bytearrayrawfilesynchronizerfactorytest Start 42: structures-primitivearraytest Start 43: structures-arraydatainformationtest Start 44: structures-basicdatainformationtest Start 45: structures-primitivedatainformationtest Start 46: structures-scriptclassestest Start 47: structures-uniondatainformationtest Start 48: structures-allprimitivetypestest 1/56 Test #1: libkasten-core-testdocumenttest .. Passed0.08 sec Start 49: structures-scriptvalueconvertertest 2/56 Test #2: libkasten-core-testdocumentfilesynchronizertest ..***Failed0.08 sec * Start testing of TestDocumentFileSynchronizerTest * Config: Using QtTest library 5.15.8, Qt 5.15.8 (x86_64-little_endian-lp64 shared (dynamic) release build; by GCC 13.0.1 20230304 (Red Hat 13.0.1-0)), fedora 39 PASS : TestDocumentFileSynchronizerTest::initTestCase() PASS : TestDocumentFileSynchronizerTest::testLoadFromFile() FAIL! : TestDocumentFileSynchronizerTest::testLoadSaveFile() 'testDocument != nullptr' returned FALSE. () Loc: [/home/tkloczko/rpmbuild/BUILD/okteta-0.26.10/libs/kasten/core/tests/testdocumentfilesynchronizertest.cpp(80)] QWARN : TestDocumentFileSynchronizerTest::testLoadReloadFile() QIODevice::write (QFile, "/home/tkloczko//.kde-unit-test//testdocumentfile1synchronizertest//test1.data"): device not open FAIL! : TestDocumentFileSynchronizerTest::testLoadReloadFile() 'testDocument != nullptr' returned FALSE. () Loc: [/home/tkloczko/rpmbuild/BUILD/okteta-0.26.10/libs/kasten/core/tests/testdocumentfilesynchronizertest.cpp(164)] QWARN : TestDocumentFileSynchronizerTest::testChangeFile()
[NeoChat] [Bug 467539] Conversation list sidebar is broken
https://bugs.kde.org/show_bug.cgi?id=467539 Tobias Fella changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Tobias Fella --- Fixed in https://invent.kde.org/network/neochat/-/merge_requests/822 Will be released in 23.04 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 467540] New: View -> Continuous (Off) does not prevent Mouse Scroll or Up/Down to go to next page
https://bugs.kde.org/show_bug.cgi?id=467540 Bug ID: 467540 Summary: View -> Continuous (Off) does not prevent Mouse Scroll or Up/Down to go to next page Classification: Applications Product: okular Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: PDF backend Assignee: okular-de...@kde.org Reporter: xpressra...@gmail.com Target Milestone: --- SUMMARY *** View -> Continuous (Off) does not prevent Mouse Scroll or Up/Down to go to next page. Only should go to next page when pressing Space bar or Go -> Next Page This behavior works as expected in Evince. NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Open a pdf document in Oular 2. Select View -> View Mode -> Single Page 3. Select View -> View Mode -> Continuous (Off) OBSERVED RESULT Mouse Scroll (or Keyboard Up/Down button) to bottom of the page goes to next page. Same behavior on top of the document on that page (goes to previous page) EXPECTED RESULT It should not go to next/previous page on Mouse Scroll or Up/Down key. Only should go to next page when selecting Go-> Next Page or when pressing Space. There can also be a popup menu option to go to next page (right click). This would prevent okular from jumping to random pages, when not desired. View -> View Mode -> Continuous (On) can still work just like how it is working now. This behavior works correctly in Evince. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.26.1 KDE Frameworks Version: 5.99.0 Qt Version: 5.15.6 ADDITIONAL INFORMATION Apparently, it seems to show same behavior on 22.12.3 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 467539] New: Conversation list sidebar is broken
https://bugs.kde.org/show_bug.cgi?id=467539 Bug ID: 467539 Summary: Conversation list sidebar is broken Classification: Applications Product: NeoChat Version: 23.01.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: mic...@lebihan.pl CC: c...@carlschwan.eu Target Milestone: --- Created attachment 157399 --> https://bugs.kde.org/attachment.cgi?id=157399=edit Main window SUMMARY There is a layout issue with the conversations list sidebar STEPS TO REPRODUCE 1. Open NeoChat 2. Open a conversation 3. Notice issues with the layout of the sidebar SOFTWARE/OS VERSIONS Windows: Windows 11 Pro 22H2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Okular] Segmentation fault Qt v5.15.4 Okular okular 22.04.3
Hello list: I was redirected here from the okular.devel list as bureaucracy normally settles in and does. Hopefully I won't have to post the backtrace of this segmentation fault on every list out there. Am I? This issue does not happen with other viewers, such as xpdf [New LWP 3071] qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 1375, resource id: 18983702, major code: 40 (TranslateCoords), minor code: 0 [New LWP 3072] [LWP 3071 exited] [LWP 3072 exited] [New LWP 3073] [New LWP 3074] [LWP 3073 exited] [New LWP 3075] Thread 8 "Okular::TextPag" received signal SIGSEGV, Segmentation fault. [Switching to LWP 3074] 0x7fffe749be4a in ?? () from /usr/lib/libpoppler.so.121 (gdb) bt #0 0x7fffe749be4a in ?? () from /usr/lib/libpoppler.so.121 #1 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #2 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #3 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #4 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #5 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #6 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #7 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #8 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #9 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #10 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #11 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #12 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #13 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #14 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #15 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #16 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #17 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #18 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #19 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #20 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #21 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #22 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #23 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #24 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #25 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #26 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #27 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #28 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #29 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #30 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #31 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #32 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 --Type for more, q to quit, c to continue without paging-- #33 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #34 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #35 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #36 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #37 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #38 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #39 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #40 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #41 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #42 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #43 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #44 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #45 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #46 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #47 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #48 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #49 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #50 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #51 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #52 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #53 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #54 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #55 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #56 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #57 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #58 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #59 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #60 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #61 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #62 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #63 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #64 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121 #65 0x7fffe749c19f in ?? () from /usr/lib/libpoppler.so.121
[plasmashell] [Bug 467536] [WAYLAND] Task Switcher window appears dim (unfocused)
https://bugs.kde.org/show_bug.cgi?id=467536 --- Comment #1 from Samuel --- Created attachment 157398 --> https://bugs.kde.org/attachment.cgi?id=157398=edit Task switcher in Plasma X11 session Note: See the brightness difference in Task Switcher window between Wayland and X11 sessions. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 466679] Discover can't handle UEFI Secure Boot firmware updates
https://bugs.kde.org/show_bug.cgi?id=466679 --- Comment #4 from ternoma...@gmail.com --- On laptop Samsung NP670 there is another error message: "failed to write data to efivarfs: Error writing to file descriptor: Invalid argument". I can also confirm that the problem with "THE INPUT IS NOT OF CABINET FORMAT" can be seen on HP desktop PC UEFI update. -- You are receiving this mail because: You are watching all bug changes.
[kontact] [Bug 467538] New: Kontact not showing images in mail (but works in Kmail)
https://bugs.kde.org/show_bug.cgi?id=467538 Bug ID: 467538 Summary: Kontact not showing images in mail (but works in Kmail) Classification: Applications Product: kontact Version: 5.22.2 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: mail Assignee: kdepim-b...@kde.org Reporter: st...@hotmail.com Target Milestone: --- SUMMARY When receiving a email with an inline image, Kontact do not show the image in the email. However, when replying to this specific email, then the image show in the reply email (Re : ). Also, if I open Kmail instead of Kontact, the image appears in the received email. STEPS TO REPRODUCE 1. Open an email with an inline image. 2. No image appears when reading the email. 3. When opening the email directly with Kmail, the image shows. When replying to the received email in Kontact, the image now appears in the replying email window. EXPECTED RESULT Image shows in all received emails. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Manjaro (available in About System) KDE Plasma Version: 5.26.5 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 467537] New: Labels in login screen are cropped
https://bugs.kde.org/show_bug.cgi?id=467537 Bug ID: 467537 Summary: Labels in login screen are cropped Classification: Applications Product: NeoChat Version: 23.01.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: mic...@lebihan.pl CC: c...@carlschwan.eu Target Milestone: --- Created attachment 157397 --> https://bugs.kde.org/attachment.cgi?id=157397=edit Login screen SUMMARY Labels in login screen are cropped STEPS TO REPRODUCE 1. Set language to French 2. Start a fresh install 3. Notice that labels are cropped OBSERVED RESULT Please see screenshot EXPECTED RESULT Labels should not be cropped SOFTWARE/OS VERSIONS Windows: Windows 11 pro 22H2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 452628] Can not find a part of a word in a filename
https://bugs.kde.org/show_bug.cgi?id=452628 --- Comment #7 from tagwer...@innerjoin.org --- If you want baloo to find you "example" when you search for "xample", that's a feature request 8-) However, in dolphin, that you get a different behavour searching dependent on whether you have baloo enabled or not, or if you are searching from a folder indexed or not indexed by baloo, that is confusing. I'd flag that as a bug... -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467536] New: [WAYLAND] Task Switcher window appears dim (unfocused)
https://bugs.kde.org/show_bug.cgi?id=467536 Bug ID: 467536 Summary: [WAYLAND] Task Switcher window appears dim (unfocused) Classification: Plasma Product: plasmashell Version: 5.27.2 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: samping...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 Created attachment 157396 --> https://bugs.kde.org/attachment.cgi?id=157396=edit Task switcher appearance in Wayland session SUMMARY The task switcher in Plasma Wayland session appears dim and dull as compared to Plasma X11 session. STEPS TO REPRODUCE 1. Log-in to Plasma Wayland session 2. Press and hold Alt+tab. 3. The task switcher appears dim and dull as compared to X11 session. OBSERVED RESULT In Plasma Wayland session, the task switcher window that shows up when you alt+tab to switch windows appear very dull and appears to be "unfocused". EXPECTED RESULT The task switcher window work as it already does in X11 session - focused and bright. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103 Qt Version: 5.15.8 ADDITIONAL INFORMATION I have tested the various task switchers - Breeze, Thumbnail Grid, Cover/Flip Switch etc. They all appear dim in Wayland session as compared to X11 session. -- You are receiving this mail because: You are watching all bug changes.
[kfontview] [Bug 467535] New: No popup with information about character when selecting "All characters" view
https://bugs.kde.org/show_bug.cgi?id=467535 Bug ID: 467535 Summary: No popup with information about character when selecting "All characters" view Classification: Applications Product: kfontview Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: f.alexander.wi...@gmail.com Target Milestone: --- SUMMARY When I inspect a font like EB Garamond (https://github.com/georgd/EB-Garamond) with many characters for niche use cases, like historical floral hearts, I'd like to easily find out a symbol's code point. When I select a preview of the type "Unicode Block", I get a popup with this information when I hover with the cursor over the symbol. However, there is no popup when one select the "All Characters" preview type. STEPS TO REPRODUCE 1. Open e.g. /usr/share/fonts/LiberationSans-Regular.ttf in kfontview 2. Select "Unicode Block: Basic Latin" as preview 3. Hover over character 4. Select "All Characters" as preview 5. Hover over character OBSERVED RESULT In the first case, one gets a popup with information like this: Category Letter, Uppercase UCS-4 U+ 41 UTF-160x 41 UTF-8 0x41 XML Decimal Entity In the second case, there is no such popup. EXPECTED RESULT The same popup, regardless of preview type. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230315 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.4-1-default (64-bit) Graphics Platform: X11 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 462572] Autohidden top panel does not autohide after startup until hovered or interacted with once
https://bugs.kde.org/show_bug.cgi?id=462572 --- Comment #12 from kinghat --- (In reply to kinghat from comment #7) > i used to have this same issue but my experience is on par with nate now on: > > Operating System: Fedora Linux 37 > KDE Plasma Version: 5.27.2 > KDE Frameworks Version: 5.103.0 > Qt Version: 5.15.8 > Kernel Version: 6.1.18-200.fc37.x86_64 (64-bit) > Graphics Platform: Wayland correction, ive had my auto-hide panel stick open after login twice since i posted this. unsure of the conditions that cause it. last one was after an update reboot. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467528] Images Locked in Finder are not obvious in Digikam and won't copy or delete.
https://bugs.kde.org/show_bug.cgi?id=467528 caulier.gil...@gmail.com changed: What|Removed |Added Component|general |Database-Media CC||caulier.gil...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 464257] Layer effects not saved if they're the only thing changed.
https://bugs.kde.org/show_bug.cgi?id=464257 Tiar changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED --- Comment #6 from Tiar --- Setting it to fixed, then :) Thanks for testing! -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #35 from caulier.gil...@gmail.com --- Hi Geof, yesterday, the new gmic + gmicqt version 3.2.2 have been released. We are for now in 3.1.6. I will update all code before to conclude. And yes, i see the improvements also in my computer, and also few crashes in specific filters. I still few way to study for improvements : - Use gcc instead clang as compiler. i remember a thread in gmic issue about the right compiler to use. - libfftw under mac which is problematic. I read also an older thread about this subject. I'm not sure if it's always the case. So wait a little bit. perhaps an update of code will fix last crashes. If no, well we will need to identify which filters crash exactly, and found something common to report to gmic team. Best Gilles -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467255] Kate crashing when clicking "clear" in the bottom textbox on the find/replace window
https://bugs.kde.org/show_bug.cgi?id=467255 Waqar Ahmed changed: What|Removed |Added Latest Commit|https://invent.kde.org/util |https://invent.kde.org/util |ities/kate/commit/5ed1c9f72 |ities/kate/commit/d9abb86d2 |55fb540f2b7ceae102da2f2278f |5e9941a40afcdf72589111a5a24 |3e41|dc67 --- Comment #2 from Waqar Ahmed --- Git commit d9abb86d25e9941a40afcdf72589111a5a24dc67 by Waqar Ahmed. Committed on 18/03/2023 at 17:09. Pushed by waqar into branch 'release/23.04'. Search: Fix crash on clicking clear m_curResults was null (cherry picked from commit 5ed1c9f7255fb540f2b7ceae102da2f2278f3e41) M +3-1addons/search/SearchPlugin.cpp https://invent.kde.org/utilities/kate/commit/d9abb86d25e9941a40afcdf72589111a5a24dc67 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467531] Changing any setting causes "Restart required"
https://bugs.kde.org/show_bug.cgi?id=467531 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 467534] New: Log access to the credentials store
https://bugs.kde.org/show_bug.cgi?id=467534 Bug ID: 467534 Summary: Log access to the credentials store Classification: Applications Product: kwalletmanager Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: va...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- SUMMARY It'd be great if kwalletmanager automatically logged all access (read/write/granting) to the credentials store: including time of access, which credentials were access, application path, the user name under which it ran and if it were successful or not. IMO this could enhance the security. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467359] Request: re-enable running Dolphin as sudo
https://bugs.kde.org/show_bug.cgi?id=467359 --- Comment #4 from David --- (In reply to Ben Bonacci from comment #3) > > *** This bug has been marked as a duplicate of bug 179678 *** But this is not a duplicate: the linked bug report is about adding functionality for requesting privileges when needed. This bug report is about not removing functionality until the replacement is already available, which it isn't. -- You are receiving this mail because: You are watching all bug changes.
[kwalletmanager] [Bug 467533] New: Allow only application to access its stored credentials
https://bugs.kde.org/show_bug.cgi?id=467533 Bug ID: 467533 Summary: Allow only application to access its stored credentials Classification: Applications Product: kwalletmanager Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: va...@kde.org Reporter: pos...@posteo.eu Target Milestone: --- SUMMARY As far as I am informed, right now, once an application makes use of the credentials store (kwallet), it can basically access all credentials, including those of other applications. It'd therefore be a security enhancement if it could only access credentials which are associated with this very application. One way to to associate it, could be to check if it started under a certain path like `/usr/bin/my-application`. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 467532] New: Default log out option is not useful
https://bugs.kde.org/show_bug.cgi?id=467532 Bug ID: 467532 Summary: Default log out option is not useful Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: david.cortes.riv...@gmail.com Target Milestone: --- SUMMARY The default logout option is "log out" of a user session. This is not a reasonable thing to put as default, since very seldom would someone using a desktop computer want to do that. The year is 2023. Most desktop computers have a single user, who wants to shut down the computer when done using it. STEPS TO REPRODUCE 1. Press Ctrl+Alt+Del or trigger the logout dialog through some other way. OBSERVED RESULT Offers me to "log out". EXPECTED RESULT Should offer me to either restart the computer (for Ctrl+Alt+Del), shut it down (for buttons elsewhere), or perhaps hibernate. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 467530] K3b - wrong (less) permissions to some programms
https://bugs.kde.org/show_bug.cgi?id=467530 Andreas changed: What|Removed |Added CC||andreaskleine.onl...@web.de -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 467530] K3b - wrong (less) permissions to some programms
https://bugs.kde.org/show_bug.cgi?id=467530 --- Comment #2 from Andreas --- Created attachment 157395 --> https://bugs.kde.org/attachment.cgi?id=157395=edit screen shot of the burner device found -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 467530] K3b - wrong (less) permissions to some programms
https://bugs.kde.org/show_bug.cgi?id=467530 --- Comment #1 from Andreas --- Created attachment 157394 --> https://bugs.kde.org/attachment.cgi?id=157394=edit dialog message about the wrong/missing permissions -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 467531] New: Changing any setting causes "Restart required"
https://bugs.kde.org/show_bug.cgi?id=467531 Bug ID: 467531 Summary: Changing any setting causes "Restart required" Classification: Applications Product: systemsettings Version: 5.27.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_baloo Assignee: baloo-bugs-n...@kde.org Reporter: stefan.bru...@rwth-aachen.de CC: plasma-b...@kde.org Target Milestone: --- Created attachment 157393 --> https://bugs.kde.org/attachment.cgi?id=157393=edit Erroneous dialog SUMMARY baloo picks up changes of the config file, there is no need to restart the session. STEPS TO REPRODUCE 1. Open "File Search" 2. Change any setting 3. Click on "Apply" OBSERVED RESULT Inline dialog: "The system must be restarted before these changes will take effect. [Restart]". EXPECTED RESULT Update the config file. Done. SOFTWARE/OS VERSIONS Frameworks 5.104.0 Qt 5.18.8 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[k3b] [Bug 467530] New: K3b - wrong (less) permissions to some programms
https://bugs.kde.org/show_bug.cgi?id=467530 Bug ID: 467530 Summary: K3b - wrong (less) permissions to some programms Classification: Applications Product: k3b Version: 21.12.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Burning/Hardware Assignee: k...@kde.org Reporter: andreaskleine.onl...@web.de CC: mich...@jabster.pl, tr...@kde.org Target Milestone: --- Created attachment 157392 --> https://bugs.kde.org/attachment.cgi?id=157392=edit screen shot after the second permission change request SUMMARY *** NOTE: This is NOT a crash report; there is a problem with the rights for cdrecord: /usr/bin/wodim; cdrdao: /usr/bin/cdrdao; growisofs: /usr/bin/growisofs STEPS TO REPRODUCE 1. k3b installed 2. open "Einstellungen - K3b-einrichten" goto "Programme - Berechtigungen" 3. give the requested permissions through clicking the button "Berechtigungen ändern" 4. click "ok" to leave the dialog 5. open "Einstellungen - K3b-einrichten" again goto "Programme - Berechtigungen" again 6. new permissions are shown by K3b, so i push the button "Berechtigungen ändern" again to confirm the requested change again. confirm the button "ok" to close the dialog. OBSERVED RESULT the message is shown, that are not enough permissions for the listed programms when you enter the "Einstellungen - K3b-einrichten"-"Programme - Berechtigungen" again, K3b makes no further suggestions to give the right permissions back to the first change request EXPECTED RESULT no error message about wrong permissions to the programms so i can burn a medium SOFTWARE/OS VERSIONS Linux/KDE Plasma:Kubuntu 22.04.2 LTS (available in About System) 5.15.0-67-generic (64-bit); X11 KDE Plasma Version: 5.24.7 KDE Frameworks Version: 5.92.0 Qt Version:5.15.3 ADDITIONAL INFORMATION three screen shots -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467529] Computer is a brick after installing system updates
https://bugs.kde.org/show_bug.cgi?id=467529 --- Comment #3 from php4...@gmail.com --- Created attachment 157391 --> https://bugs.kde.org/attachment.cgi?id=157391=edit Contents of [ScreenMapping] in config file This was the contents of the [ScreenMapping] section in the abovementioned config file. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 452628] Can not find a part of a word in a filename
https://bugs.kde.org/show_bug.cgi?id=452628 Stefan Brüns changed: What|Removed |Added CC||stefan.bruens@rwth-aachen.d ||e --- Comment #6 from Stefan Brüns --- Why does this bugzilla instance disallow any priorization, or categorizing? This is not a bug, but currently intentional (so close this as Resolved/Intentional?). But marking this as feature is not possible ... -- You are receiving this mail because: You are watching all bug changes.
[Akonadi] [Bug 332195] Allow to disable akonadi_baloo_indexer
https://bugs.kde.org/show_bug.cgi?id=332195 Stefan Brüns changed: What|Removed |Added Resolution|--- |UNMAINTAINED CC||stefan.bruens@rwth-aachen.d ||e Status|REOPENED|RESOLVED --- Comment #32 from Stefan Brüns --- There no longer is any relationship between akonadi and baloo indexes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467529] Computer is a brick after installing system updates
https://bugs.kde.org/show_bug.cgi?id=467529 --- Comment #2 from php4...@gmail.com --- This fixed it for me: https://forum.manjaro.org/t/programs-only-open-with-krunner-desktop-icons-missing-after-2-12-2023-update/133957/31 > The issue seems to be within the file > .config/plasma-org.kde.plasma.desktop-appletsrc, > specifically within this section: > > [ScreenMapping] > itemsOnDisabledScreens= > > After deleting the section (best to use vim or something that works on ~20 MB > file), and rebooting, everything is back to normal. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 445825] Baloo indexer gives more priority to content rather than file name
https://bugs.kde.org/show_bug.cgi?id=445825 Stefan Brüns changed: What|Removed |Added CC||stefan.bruens@rwth-aachen.d ||e --- Comment #6 from Stefan Brüns --- Several incorrect assumptions: 1. The Baloo indexer does not prioritize content at all 2. KRunner prioritizes by modification time 3. You can limit your searches by prefixing the term with either "content:" or "filename:" -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467529] Computer is a brick after installing system updates
https://bugs.kde.org/show_bug.cgi?id=467529 --- Comment #1 from php4...@gmail.com --- Created attachment 157390 --> https://bugs.kde.org/attachment.cgi?id=157390=edit output of journalctl -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 461400] Kmail stays offline after wakeup from suspend to ram
https://bugs.kde.org/show_bug.cgi?id=461400 --- Comment #18 from Alej --- Still present in recent update 5.27.3 KDE Neon 5.27 (22.04 jammy) -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 439420] crash when switching games
https://bugs.kde.org/show_bug.cgi?id=439420 --- Comment #8 from Stephan Kulow --- Created attachment 157389 --> https://bugs.kde.org/attachment.cgi?id=157389=edit golf save game But I compiled an old version without BH and still can't reproduce. For that I load the attached game, move the three final cards and after the animation press "New Game" on the toolbar and pick klondike. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 467529] New: Computer is a brick after installing system updates
https://bugs.kde.org/show_bug.cgi?id=467529 Bug ID: 467529 Summary: Computer is a brick after installing system updates Classification: Plasma Product: plasmashell Version: master Platform: Manjaro OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: php4...@gmail.com CC: k...@davidedmundson.co.uk Target Milestone: 1.0 STEPS TO REPRODUCE 1. on Manjaro Linux... 2. install latest system updates from the system tray whatever thingie 3. reboot OBSERVED RESULT My desktop is completely empty, with the usual background image but no icons. I can't launch any application. When I try to launch anything, like Google Chrome, Konsole, Dolphine, Kate, etc., the loading icon shows up for a few seconds and then nothing, not even an error message. By going to Ctrl+Alt+F2 and logging into the virtual tty, I ran ``` DISPLAY=:0 konsole DISPLAY=:0 dolphin DISPLAY=:0 google-chrome-stable ``` and that succesfully runs the applications in the first screen (I see them open when I go back to ctrl+Alt+F1). All with no error message. This is the output of: ``` journalctl --boot=-1 --priority=4 --no-pager ``` Wait, seriously I cannot copy and paste images here? Oh FFS (going to attach it). EXPECTED RESULT well I don't think I need to explain it. SOFTWARE/OS VERSIONS Launching System Settings / About this system doesn't work, and I don't know the command to launch it from the tty (tried a few guesses). -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 467528] New: Images Locked in Finder are not obvious in Digikam and won't copy or delete.
https://bugs.kde.org/show_bug.cgi?id=467528 Bug ID: 467528 Summary: Images Locked in Finder are not obvious in Digikam and won't copy or delete. Classification: Applications Product: digikam Version: 8.0.0 Platform: macOS (DMG) OS: macOS Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: digikam-bugs-n...@kde.org Reporter: gski...@gmail.com Target Milestone: --- SUMMARY My camera has a button to protect images with a little key icon. When I get a good shot, I press that button to protect it from accidental deletion or to be able to find it easier. When the image are on the Mac, these are "Locked" (File Info - General). Images that are Locked are not obvious to see in Digikam. They cannot be moved or deleted. Digikam does not tell us why nothing is happening to these images. Since I am aware of this, I need to go into Finder and uncheck the "Locked" option and then they can be mangaed in Digikam like normal. It would be nice to have an indicator in Digikam to identify these and remind me why they can't be moved or deleted. Maybe an icon on thumbnail view? or other area? Option to unlock the images from within Digikam GUI? STEPS TO REPRODUCE 1. Protect image in camera 2. Finder considers these Locked. 3. Cannot move or delete images within Digikam until unlocked on a system level using Finder. OBSERVED RESULT Cannot move or delete images within Digikam until unlocked on a system level. EXPECTED RESULT GUI option to be able to unlock the images or at least see why these operations cannot be performed AND/OR an icon on the thumbnail telling me that this is a locked file. SOFTWARE/OS VERSIONS Windows: macOS: Only tested on MACOS 12.6.3 Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: 5.15.8 ADDITIONAL INFORMATION digiKam-8.0.0-20230318T115132-MacOS-x86-64.pkg -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465865] Enabling the "sort applications alphabetically" setting results in nonsensical positioning of separator items
https://bugs.kde.org/show_bug.cgi?id=465865 Joshua Goins changed: What|Removed |Added Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas |ma/plasma-desktop/commit/90 |ma/plasma-desktop/commit/d4 |ad64ba638649b68cf2ffb7f68e2 |92a691d44a2878eb3c189219dc0 |27e86a8b8f1 |4260294bb77 --- Comment #11 from Joshua Goins --- Git commit d492a691d44a2878eb3c189219dc04260294bb77 by Joshua Goins. Committed on 18/03/2023 at 15:45. Pushed by redstrate into branch 'Plasma/5.27'. applets/kicker: Hide separators when sorted alphabetically Users are able to manually add separator items at custom positions in their menu structures. When they do so, the location of these separators are inherently custom, and only make sense when the menu structure is being displayed in its custom order. When using the option to display everything alphabetically, the separators' custom position no longer exists and any automatic placement becomes nonsensical. Currently, the separators get sorted to the beginning of the list, which looks quite weird. This commit instead hides the separators when sorting alphabetically. Only Kicker is affected by this change; the underlying model providing the items is unchanged. FIXED-IN: 5.27.4 (cherry picked from commit 90ad64ba638649b68cf2ffb7f68e227e86a8b8f1) M +3-1applets/kicker/package/contents/ui/ItemListDelegate.qml M +2-0applets/kicker/package/contents/ui/ItemListDialog.qml M +1-1applets/kicker/package/contents/ui/ItemListView.qml https://invent.kde.org/plasma/plasma-desktop/commit/d492a691d44a2878eb3c189219dc04260294bb77 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 465865] Enabling the "sort applications alphabetically" setting results in nonsensical positioning of separator items
https://bugs.kde.org/show_bug.cgi?id=465865 Joshua Goins changed: What|Removed |Added Status|ASSIGNED|RESOLVED Version Fixed In||5.27.4 Latest Commit||https://invent.kde.org/plas ||ma/plasma-desktop/commit/90 ||ad64ba638649b68cf2ffb7f68e2 ||27e86a8b8f1 Resolution|--- |FIXED --- Comment #10 from Joshua Goins --- Git commit 90ad64ba638649b68cf2ffb7f68e227e86a8b8f1 by Joshua Goins. Committed on 18/03/2023 at 15:44. Pushed by redstrate into branch 'master'. applets/kicker: Hide separators when sorted alphabetically Users are able to manually add separator items at custom positions in their menu structures. When they do so, the location of these separators are inherently custom, and only make sense when the menu structure is being displayed in its custom order. When using the option to display everything alphabetically, the separators' custom position no longer exists and any automatic placement becomes nonsensical. Currently, the separators get sorted to the beginning of the list, which looks quite weird. This commit instead hides the separators when sorting alphabetically. Only Kicker is affected by this change; the underlying model providing the items is unchanged. FIXED-IN: 5.27.4 M +3-1applets/kicker/package/contents/ui/ItemListDelegate.qml M +2-0applets/kicker/package/contents/ui/ItemListDialog.qml M +1-1applets/kicker/package/contents/ui/ItemListView.qml https://invent.kde.org/plasma/plasma-desktop/commit/90ad64ba638649b68cf2ffb7f68e227e86a8b8f1 -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 467527] New: Never quits when --nonotify and --region is specified
https://bugs.kde.org/show_bug.cgi?id=467527 Bug ID: 467527 Summary: Never quits when --nonotify and --region is specified Classification: Applications Product: Spectacle Version: 23.03.80 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: m...@baloneygeek.com Reporter: magunasu@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Run `spectacle --background --nonotify --region --output test.png` 2. Take screenshot 3. Notice how the application never quits OBSERVED RESULT Spectacle does not quit, process just sits there. EXPECTED RESULT Spectacle to take the screenshot and quit, like previously. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.6-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 3700X 8-Core Processor Memory: 47.0 GiB of RAM Graphics Processor: AMD Radeon RX 6600 XT Manufacturer: Gigabyte Technology Co., Ltd. Product Name: B450M DS3H ADDITIONAL INFORMATION It seems to quit if you then take another screenshot in another mode, such as `spectacle --background --nonotify --fullscreen --output test2.png` -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 467526] New: dolphin crashes where deleting file and folder
https://bugs.kde.org/show_bug.cgi?id=467526 Bug ID: 467526 Summary: dolphin crashes where deleting file and folder Classification: Applications Product: dolphin Version: 22.12.3 Platform: openSUSE OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: devguy...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Application: dolphin (22.12.3) Qt Version: 5.15.8 Frameworks Version: 5.104.0 Operating System: Linux 6.2.4-1-default x86_64 Windowing System: X11 Distribution: openSUSE Tumbleweed DrKonqi: 5.27.2 [KCrashBackend] -- Information about the crash: This has occured 2 time, I self a group of folder to be delete, press the delete key and dolphin will crash The crash can be reproduced every time. -- Backtrace: Application: Dolphin (dolphin), signal: Segmentation fault [KCrash Handler] #4 0x7f4b2fd3c77e in KFileItemModel::expandedParentsCount(KFileItemModel::ItemData const*) () from /lib64/libdolphinprivate.so.5 #5 0x7f4b2fd6ae39 in KItemListView::hasSiblingSuccessor(int) const () from /lib64/libdolphinprivate.so.5 #6 0x7f4b2fd6bcec in KItemListView::updateSiblingsInformation(int, int) () from /lib64/libdolphinprivate.so.5 #7 0x7f4b2fd7054e in KItemListView::slotItemsRemoved(KItemRangeList const&) () from /lib64/libdolphinprivate.so.5 #8 0x7f4b2dd1338d in ?? () from /lib64/libQt5Core.so.5 #9 0x7f4b2fd2a2b5 in KItemModelBase::itemsRemoved(KItemRangeList const&) () from /lib64/libdolphinprivate.so.5 #10 0x7f4b2fd43b87 in KFileItemModel::slotItemsDeleted(KFileItemList const&) () from /lib64/libdolphinprivate.so.5 #11 0x7f4b2dd1338d in ?? () from /lib64/libQt5Core.so.5 #12 0x7f4b2f8083d5 in KCoreDirLister::itemsDeleted(KFileItemList const&) () from /lib64/libKF5KIOCore.so.5 #13 0x7f4b2f80fd79 in ?? () from /lib64/libKF5KIOCore.so.5 #14 0x7f4b2f801f94 in ?? () from /lib64/libKF5KIOCore.so.5 #15 0x7f4b2f804a9a in ?? () from /lib64/libKF5KIOCore.so.5 #16 0x7f4b2dd1338d in ?? () from /lib64/libQt5Core.so.5 #17 0x7f4b2efd89b5 in KDirWatch::deleted(QString const&) () from /lib64/libKF5CoreAddons.so.5 #18 0x7f4b2dd07d00 in QObject::event(QEvent*) () from /lib64/libQt5Core.so.5 #19 0x7f4b2e9a544e in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /lib64/libQt5Widgets.so.5 #20 0x7f4b2dcdc1e8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () from /lib64/libQt5Core.so.5 #21 0x7f4b2dcdf181 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /lib64/libQt5Core.so.5 #22 0x7f4b2dd34413 in ?? () from /lib64/libQt5Core.so.5 #23 0x7f4b2ba67a90 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x7f4b2ba67e48 in ?? () from /lib64/libglib-2.0.so.0 #25 0x7f4b2ba67edc in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x7f4b2dd33c16 in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #27 0x7f4b2dcdac5b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #28 0x7f4b2dce2dc6 in QCoreApplication::exec() () from /lib64/libQt5Core.so.5 #29 0x558fd29d6719 in ?? () #30 0x7f4b2d42caf0 in __libc_start_call_main () from /lib64/libc.so.6 #31 0x7f4b2d42cbb9 in __libc_start_main_impl () from /lib64/libc.so.6 #32 0x558fd29d6d85 in ?? () [Inferior 1 (process 9390) detached] Reported using DrKonqi -- You are receiving this mail because: You are watching all bug changes.
[kpat] [Bug 439420] crash when switching games
https://bugs.kde.org/show_bug.cgi?id=439420 Stephan Kulow changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #7 from Stephan Kulow --- ok, the problem is that fedora didn't enable the blackhole solver for golf but the developers used version with it, so the alternative solver bitrotted. I removed it in master (so you wouldn't have any solver unless fedora enables it). I'm confident that the bug is there, but I'll try to win golf for a bit. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 467518] KWrite doesn't respect initial window size setting set in System Settings
https://bugs.kde.org/show_bug.cgi?id=467518 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from Paul Worrall --- Quoting from the message that appears at the top of the settings dialog: Some applications set their own geometry after starting, overriding your initial settings for size and position. To enforce these settings, also force the property "Ignore requested geometry" to "Yes". So, you need to add the property "Ignore requested geometry" and set it to "Force" -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 467525] Neochat crashes on startup
https://bugs.kde.org/show_bug.cgi?id=467525 --- Comment #5 from Tobias Fella --- Why not? The second backtrace is still missing debug symbols -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 422996] Digikam Crash with GMicQt plugin on Mac Mojave
https://bugs.kde.org/show_bug.cgi?id=422996 --- Comment #34 from Geoff King --- Hi, This is so much better. Thank You. I was able to use it and play with most filters now with no issues. The original report pointed to "Film Simulate" and that now works fine - no crashes after several processed photos with different settings. Also an earlier report pointed to "Artistic > Cartoon" and that now works fine also. I'm now using digiKam-8.0.0-20230318T115132-MacOS-x86-64.pkg on a MacBook Air 2022 12.6.3. However, I still did get a few repeatable crashes but they appear to be filter specific, for example, Colors > Mixer [LAB] or Color Temperature seems to always crash quickly when entering. I can report those separately if you prefer. Should I make a new bug report here or somewhere else? As it is now this is a big improvement and usable, if I stay away from a few specific filters. -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 467525] Neochat crashes on startup
https://bugs.kde.org/show_bug.cgi?id=467525 --- Comment #4 from aron...@gmail.com --- (In reply to Tobias Fella from comment #3) > Not really, can you install org.kde.neochat.Debug and try that again? probably not... this one? PID: 12907 (neochat) UID: 1000 (aronkvh) GID: 1000 (aronkvh) Signal: 6 (ABRT) Timestamp: Sat 2023-03-18 15:52:08 CET (18min ago) Command Line: neochat Executable: /app/bin/neochat Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-flatpak-org.kde.neochat-12898.scope Unit: user@1000.service User Unit: app-flatpak-org.kde.neochat-12898.scope Slice: user-1000.slice Owner UID: 1000 (aronkvh) Boot ID: 83deecd70658472388e80a46bcb48f90 Machine ID: e5f92eb519e44b4fb02f8a6905c56c34 Hostname: NeonAron Storage: /var/lib/systemd/coredump/core.neochat.1000.83deecd70658472388e80a46bcb48f90.12907.167915112800.zst (present) Disk Size: 17.7M Message: Process 12907 (neochat) of user 1000 dumped core. Found module /app/bin/neochat with build-id: d160086d56009f3cf5f121b0fb7024122d8b5a06 Found module /usr/lib/x86_64-linux-gnu/libtinfo.so.6.3 with build-id: 067cfa3302649ddd6329add4b69a37cf0e498afe Found module /usr/lib/x86_64-linux-gnu/libhunspell-1.7.so.0.0.1 with build-id: 76e0484dd16c602dc950be3c10a4e2aa0303ecb1 Found module /usr/lib/plugins/kf5/sonnet/sonnet_hunspell.so with build-id: aacff7b9e29e120a9b428dc58f1ff52780cf7ad0 Found module /usr/lib/x86_64-linux-gnu/libaspell.so.15.3.1 with build-id: e98fce907e560fbd87e9ec4a0f3e7eb6e1e81608 Found module /usr/lib/plugins/kf5/sonnet/sonnet_aspell.so with build-id: 6e4f889a3388f0e00869ba0679471f27313e2b24 Found module /usr/lib/x86_64-linux-gnu/libsqlite3.so.0.8.6 with build-id: 70e94b90c2ca41db05d1ef73f47ab59d0b3e89d7 Found module /usr/lib/plugins/sqldrivers/libqsqlite.so with build-id: bafcac649941004f83b66c7710dd8cf88be91403 Found module /usr/lib/x86_64-linux-gnu/libnss_resolve.so.2 with build-id: 7cb24b8fba927b9a00a83822b839e13e7c0dfe65 Found module /usr/lib/plugins/bearer/libqnmbearer.so with build-id: 24282570a0319a7dea3b62de74ec94a06c5df968 Found module /usr/lib/plugins/bearer/libqconnmanbearer.so with build-id: c8ed64bbb5bfaa0f2c615f1d740addcd284195ed Found module /usr/lib/plugins/bearer/libqgenericbearer.so with build-id: 2bd78135669151fee664bdd22e4ce20e9fbd93a6 Found module /usr/lib/x86_64-linux-gnu/libxcb-res.so.0.0.0 with build-id: 5cc26e12f1a339a121bd870ef59eb7ce94a5ecfa Found module /usr/lib/plugins/kf5/kwindowsystem/KF5WindowSystemX11Plugin.so with build-id: 5bd85c5e766912c2a0a03781515bbd5cf82b0590 Found module /usr/lib/plugins/kf5/kirigami/org.kde.desktop.so with build-id: 3c045c1648d929a2ad75e17cc440cf6c6c5a2610 Found module /usr/lib/x86_64-linux-gnu/libQt5MultimediaQuick.so.5.15.8 with build-id: fca1943c93157075eb648fc18fe96341413b9ce5 Found module /usr/lib/qml/QtMultimedia/libdeclarative_multimedia.so with build-id: ecb6ab4c27cb64134bb464daf0bb783027bfac45 Found module /usr/lib/qml/org/kde/quickcharts/libQuickCharts.so with build-id: bf8679cfc7d64db21a07e0a7503f9b99d8a86f2b Found module /usr/lib/qml/QtQml/Models.2/libmodelsplugin.so with build-id: 4be1fc83f5ce179b04183b9ea4f1f61c659c8394 Found module /app/lib/qml/org/kde/kquickimageeditor/libkquickimageeditorplugin.so with build-id: 854451af7b0e75e103fcd1d0a1df09ff02733b51 Found module /usr/lib/x86_64-linux-gnu/libQt5QuickParticles.so.5.15.8 with build-id: d938ecd4bc41c76e1c0758224ed05119bdaea64c Found module /usr/lib/qml/QtQuick/Particles.2/libparticlesplugin.so with build-id: a13383881a6e8c920caa69c80c56843765854c0d Found module /usr/lib/x86_64-linux-gnu/libKF5ItemModels.so.5.104.0 with build-id: 980998e607a61fd461d7175812c231d1acec877b Found module /usr/lib/qml/org/kde/kitemmodels/libitemmodelsplugin.so with build-id: 43bc3962f94c890e8f005fc6b08b3a1ea3034b3a Found module /usr/lib/qml/Qt/labs/qmlmodels/liblabsmodelsplugin.so with build-id: 63a93cc87219bce1cba8665320f31d621c8cf79d Found module /usr/lib/qml/Qt/labs/platform/libqtlabsplatformplugin.so with build-id: bd96bd08bfdbcc2b1dee3ed27e3dfa97ef861518 Found module /usr/lib/x86_64-linux-gnu/libjxl.so.0.8.1 with build-id: 20e17aaf6527f0518c27a8c10a1833aa98195702 Found module /usr/lib/qml/org/kde/sonnet/libsonnetquickplugin.so with build-id: 3f0ba501c8525bdc4984f0517cb03c69f26cfdcd Found module /usr/lib/qml/QtQuick/Templates.2/libqtquicktemplates2plugin.so with build-id: f997183cdfcf32fffd542727dc225e974ba619df Found
