[kwin] [Bug 472456] New: Windows wakes up from screen saving mode in full brightness
https://bugs.kde.org/show_bug.cgi?id=472456 Bug ID: 472456 Summary: Windows wakes up from screen saving mode in full brightness Classification: Plasma Product: kwin Version: 5.27.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: koncek.mar...@gmail.com Target Milestone: --- SUMMARY When lowering a laptop's brightness to a minimum (i. e. 0 %) by pressing the Fn keys, waiting for the screen saving (which turns off the screen) mode to activate and then moving the mouse to wake the screen, the screen has maximum brightness. It is worth mentioning that changing the brightness with Fn keys behaves as-if the brighntess was at 0 %. I. e. lowering the brightness goes to 0 %, increasing it goes to 5 %. When the brightness is above 0 %, then it wakes up to the correct previous brightness. This behaviour was also different some ~ 2 years ago, when the screen would wake up to the 5 % (?) or some other small value that was not 0 %. STEPS TO REPRODUCE 1. On a laptop, manually lower the screen's brightness to 0 %. (The screen is now almost completely black) 2. Wait for the screen saving mode to turn off the screen (not sleep, not screen dim) 3. Perform any action that wakes up the screen. (e. g. move mouse) OBSERVED RESULT Laptop screen now has 100 % brightness. EXPECTED RESULT Screen should wake up with the minimal **user-visible** screen brightness, i. e. one Fn button press away from 0 %. Which usually is 5 %. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Fedora KDE 38 (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION This issue was observer first time a few years ago. Behaviour is the same on X11 and Wayland. Behaviour is the same no matter whether external monitors are connected. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 471270] Application crashes on editing while rendering: segmentation fault
https://bugs.kde.org/show_bug.cgi?id=471270 Narcis Garcia changed: What|Removed |Added Summary|Cut non-selected clip in|Application crashes on |timeline: segmentation |editing while rendering: |fault |segmentation fault -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 472455] New: Memory leak after opening large file with lsp plugin enabled
https://bugs.kde.org/show_bug.cgi?id=472455 Bug ID: 472455 Summary: Memory leak after opening large file with lsp plugin enabled Classification: Applications Product: kate Version: 22.12.3 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: kwrite-bugs-n...@kde.org Reporter: calvinchaoc...@outlook.com Target Milestone: --- SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. Enable lsp plugin and install dart analyzer serber 2. Randomly open a large dart source file(eg. one from flutter sdk) 3. Memory will leak and the UI will become slow OBSERVED RESULT Memory leak and slow ui EXPECTED RESULT no memory leak 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.
[kdeconnect] [Bug 470215] Devices see each other "unreacheble" after pairing
https://bugs.kde.org/show_bug.cgi?id=470215 --- Comment #1 from AMajor --- Now on Windows 10 works. But on Windows 8.1 doesnt -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 462381] KIO-Extras AFC URL error
https://bugs.kde.org/show_bug.cgi?id=462381 g311571...@gmail.com changed: What|Removed |Added CC||g311571...@gmail.com Status|ASSIGNED|CONFIRMED --- Comment #5 from g311571...@gmail.com --- The above pr still doesn't be accepted -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433304] Adding a new automatically starting application generates deprecated/invalid .desktop file
https://bugs.kde.org/show_bug.cgi?id=433304 soredake changed: What|Removed |Added CC|broaden_acid002@simplelogin | |.com| -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 433304] Adding a new automatically starting application generates deprecated/invalid .desktop file
https://bugs.kde.org/show_bug.cgi?id=433304 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/3089 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415599] Add date to help DNN face recognition for baby/kid/adult distinction
https://bugs.kde.org/show_bug.cgi?id=415599 --- Comment #6 from Alexandre Belz --- Hi Craig, I agree with you, haircut would probably not be a good metadata parameter. Nevertheless, we as humans can use this as a complement to distinginuish two people having the same skull. Let's take the example of real twins. If at some date (Let's say between 2005 and 2010) Jane had long hair and Mary had cut them short, a human can know that. An good NN could progressively learn, converge, and finally do better suggestions based on this. And if from 2010 to 2015 they had the opposite haircut, NN could use the "date taken" to correlate better and suggest better. The advantage with a NN is that, provided it have access to more (meta)data it can progressively learn (but it's a bit of magic/black box) the differences, it can build a better estimation model. Let's take another example: if both sisters have same haircut, and Mary only plays the piano and Jane plays the guitar, a human will be able to distinguish the two when they play at band, even if they look the same. An ideal NN should be able to learn that also. But the learning process might be long for the NN. Finally, if Jane lives in London and Mary in Paris, the GPS coordinates could help making a guess. After all, a NN is just that : making stastistical guesses. And objective metadata are more reliable and easy to learn for a "young" NN. So back to my initial topic, i think that "date taken" and probably "location" would be great to be added to the NN. Of course, it's not on Digikam shoulders, but more on DNN research team. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469324] Cuted files/folders still listed
https://bugs.kde.org/show_bug.cgi?id=469324 --- Comment #24 from Méven --- (In reply to mozo from comment #23) > For some reason I have holded Dolphin updates. With the latest Dolphin > version there's no problem, thank you. There is actually one more related > problem but I will use another icon to open Dolphin. Thank you for letting me know, mystery solved -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437226] Login script disappears after closing and re-opening the KCM when ~/.config/autostart is a file, not a folder
https://bugs.kde.org/show_bug.cgi?id=437226 thenujan changed: What|Removed |Added Status|CONFIRMED |RESOLVED CC||sthenujan2...@gmail.com Resolution|--- |NOT A BUG --- Comment #15 from thenujan --- Closing this bug report as no one else reported the same issue in the past two years. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469354] Ctrl scroll zoom direction is inverted in dolphin detail view
https://bugs.kde.org/show_bug.cgi?id=469354 --- Comment #3 from Méven --- Do you use a mouse or a touchpad ? I would guess a mouse ? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 428094] Provide ability in gui to disable autostart for programs in /etc/xdg/autostart/
https://bugs.kde.org/show_bug.cgi?id=428094 thenujan changed: What|Removed |Added CC||sthenujan2...@gmail.com --- Comment #6 from thenujan --- (In reply to Justin Zobel from comment #1) > Likely best to split it into two tabs under Autostart > > User Startup (current layout) > Global Startup (all users) (from /etc/xdg/autostart) I think another kcm for system autostart is better as the user autostart doesn't need apply buttons or enable/disable buttons but the system autostart does need them -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 455889] Parse autostarted .desktop files and display any errors in the UI
https://bugs.kde.org/show_bug.cgi?id=455889 thenujan changed: What|Removed |Added CC||sthenujan2...@gmail.com --- Comment #1 from thenujan --- (In reply to Nate Graham from comment #0) > When using Systemd boot, the XDG .desktop file parser is used, and it's > stricter than what we use in KDE, so some slightly malformed .desktop files > fail to pass vlaidation and their apps no longer autostart, without any > error message or explanation. > > Even if the XDG parser is changed to be less strict, we should still parse > the .desktop file for anything in the KCM and display errors to the user > there, so that they know which of the entries there will fail to autostart, > why, and who is to blame. > > See also Bug 455252. Is this for handwritten desktop files that were added to .config/autostart manually? If the user added a script or application to autostart using the kcm, then the desktop file shouldn't have malformed entries. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 472454] New: AutoStart Fails To Run Non FlatPak/Snap Applications and Login/Logout Scripts
https://bugs.kde.org/show_bug.cgi?id=472454 Bug ID: 472454 Summary: AutoStart Fails To Run Non FlatPak/Snap Applications and Login/Logout Scripts Classification: Applications Product: systemsettings Version: 5.27.6 Platform: Neon OS: Linux Status: REPORTED Severity: major Priority: NOR Component: kcm_autostart Assignee: plasma-b...@kde.org Reporter: abys...@yahoo.com CC: nicolas.fe...@gmx.de Target Milestone: --- SUMMARY AutoStart will not start bash scripts or non Flatpak/Snap based installed applications. STEPS TO REPRODUCE 1. Create a bash script which attempts to start another application, calls a python script, etc... 2. Add this script to AutoStart as a login script 3. Reboot and see if it runs or 1. Add an AutoStart entry for an application that is not a Flatpak or Snap application (something installed via .deb or APT) 2. Reboot and see if it runs OBSERVED RESULT It doesn't start the application on login unless it is installed via Flatpak or Snap. Scripts don't seem to execute either. EXPECTED RESULT It starts the script or application on login. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 5.19.0-46-generic (64-bit) Graphics Platform: X11 Processors: 12 × AMD Ryzen 5 5600G with Radeon Graphics Memory: 16.0 GiB of RAM Graphics Processor: AMD Radeon RX 5500 ADDITIONAL INFORMATION This shortcut was created through the AutoStart GUI, marked executable, and placed in the ~/.config/autostart directory. [Desktop Entry] Comment[en_US]= Comment= Exec=/home/abystus/Documents/startup.sh GenericName[en_US]= GenericName= Icon=dialog-scripts MimeType= Name[en_US]=startup.sh Name=startup.sh Path=/home/abystus/Documents/ StartupNotify=true Terminal=false TerminalOptions= Type=Application X-KDE-AutostartScript=true X-KDE-SubstituteUID=false X-KDE-Username= Script: (marked executable, at location /home/abystus/Documents/): #!/bin/bash /usr/bin/python /home/abystus/Dropbox/Source/Python/setmicvolumeteams.py Do note that script could be performing any action creating a new file, starting an application, etc... For some odd reason it will not execute on login, and I've even tried creating my own .desktop file to no avail with and without Terminal=true. The python script runs fine if ran from a terminal, so I know it works. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408116] [libinput on X11] Options to set right-click are greyed out and middle-click options when using Icons view in System Settings, or in the KCMShell version, or when on Wayl
https://bugs.kde.org/show_bug.cgi?id=408116 Méven changed: What|Removed |Added CC||me...@kde.org Version Fixed In|5.20.4 |6.0 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 408116] [libinput on X11] Options to set right-click are greyed out and middle-click options when using Icons view in System Settings, or in the KCMShell version, or when on Wayl
https://bugs.kde.org/show_bug.cgi?id=408116 Méven Car changed: What|Removed |Added Status|ASSIGNED|RESOLVED Resolution|--- |FIXED Latest Commit|https://commits.kde.org/pla |https://invent.kde.org/plas |sma-desktop/809f3787555f323 |ma/plasma-desktop/-/commit/ |de2a2f96d1e8d9f13601f4c27 |6e5f60767e793e03f1e08984c04 ||d28ddf36714ca --- Comment #49 from Méven Car --- Git commit 6e5f60767e793e03f1e08984c04d28ddf36714ca by Méven Car, on behalf of Méven Car. Committed on 21/07/2023 at 04:42. Pushed by meven into branch 'master'. KCM touchpad: hide initially lmr/rml section and rightclick method M +9-4kcms/touchpad/kcm/libinput/touchpad.qml https://invent.kde.org/plasma/plasma-desktop/-/commit/6e5f60767e793e03f1e08984c04d28ddf36714ca -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[krfb] [Bug 472453] New: krfb-virtualmonitor asserts when a client connects
https://bugs.kde.org/show_bug.cgi?id=472453 Bug ID: 472453 Summary: krfb-virtualmonitor asserts when a client connects Classification: Applications Product: krfb Version: 23.04.3 Platform: Archlinux OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: grundleb...@googlemail.com Reporter: santiagocezar2...@gmail.com Target Milestone: --- SUMMARY krfb-virtualmonitor crashes right after a client connects, no image is send to the client. STEPS TO REPRODUCE 1. run `bin/krfb-virtualmonitor --name "banana" --resolution 1200x400 --password --port 5900` 2. connect from another device (using bVNC on Android in this case) 3. boom OBSERVED RESULT the program crashes when a new client connects EXPECTED RESULT the program should make a virtual monitor and display it on the client SOFTWARE/OS VERSIONS Linux: 6.4.3-arch1-2 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION Graphics: Mesa Intel® UHD Graphics 620 Commit: ce562e82bb6524b558ca9f41ac81758d6c3d34e4 terminal output: ``` new client request /usr/include/c++/13.1.1/optional:477: constexpr _Tp& std::_Optional_base_impl<_Tp, _Dp>::_M_get() [with _Tp = PipeWireCursor; _Dp = std::_Optional_base]: Assertion 'this->_M_is_engaged()' failed. fish: Job 1, 'bin/krfb-virtualmonitor --name …' terminated by signal SIGABRT (Abort) ``` ``` #0 __pthread_kill_implementation (threadid=, signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x75e9f2d3 in __pthread_kill_internal (signo=6, threadid=) at pthread_kill.c:78 #2 0x75e4fa08 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #3 0x75e38538 in __GI_abort () at abort.c:79 #4 0x760dd3b2 in std::__glibcxx_assert_fail(char const*, int, char const*, char const*) (file=file@entry=0x7fffe805b2e0 "/usr/include/c++/13.1.1/optional", line=line@entry=477, function=function@entry=0x7fffe805b248 "constexpr _Tp& std::_Optional_base_impl<_Tp, _Dp>::_M_get() [with _Tp = PipeWireCursor; _Dp = std::_Optional_base]", condition=condition@entry=0x7fffe805b000 "this->_M_is_engaged()") at /usr/src/debug/gcc/gcc/libstdc++-v3/src/c++11/debug.cc:61 #5 0x7fffe804fa5c in std::_Optional_base_impl >::_M_get() (this=) at /usr/include/c++/13.1.1/optional:477 #6 std::_Optional_base_impl >::_M_get() (this=) at /usr/include/c++/13.1.1/optional:475 #7 std::optional::operator->() (this=) at /usr/include/c++/13.1.1/optional:966 #8 PWFrameBuffer::cursorPosition() (this=) at /usr/src/debug/krfb/krfb-23.04.3/framebuffers/pipewire/pw_framebuffer.cpp:546 #9 0x55568abd in RfbServerManager::updateScreens() (this=0x555846b0 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>) at /home/santi/Cositas/Contrib/krfb/krfb/rfbservermanager.cpp:148 #10 0x5556b8a9 in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (RfbServerManager::*)()>::call(void (RfbServerManager::*)(), RfbServerManager*, void**) (f=(void (RfbServerManager::*)(class RfbServerManager * const)) 0x55568a5a , o=0x555846b0 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>, arg=0x7fffd440) at /usr/include/qt/QtCore/qobjectdefs_impl.h:152 #11 0x5556b51b in QtPrivate::FunctionPointer::call, void>(void (RfbServerManager::*)(), RfbServerManager*, void**) (f=(void (RfbServerManager::*)(class RfbServerManager * const)) 0x55568a5a , o=0x555846b0 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>, arg=0x7fffd440) at /usr/include/qt/QtCore/qobjectdefs_impl.h:185 #12 0x5556ae67 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x5572b810, r=0x555846b0 <(anonymous namespace)::Q_QGS_s_instance::innerFunction()::holder>, a=0x7fffd440, ret=0x0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:418 #13 0x766d1237 in QtPrivate::QSlotObjectBase::call(QObject*, void**) (a=0x7fffd440, r=, this=0x5572b810, this=, r=, a=) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #14 doActivate(QObject*, int, void**) (sender=0x556daee0, signal_index=3, argv=0x7fffd440) at kernel/qobject.cpp:3925 #15 0x766d2d6f in QTimer::timeout(QTimer::QPrivateSignal) (this=, _t1=...) at .moc/moc_qtimer.cpp:205 #16 0x766c3cee in QObject::event(QEvent*) (this=0x556daee0, e=0x7fffd5b0) at kernel/qobject.cpp:1324 #17 0x7737893f in QApplicationPrivate::notify_helper(QObject*, QEvent*) (this=, receiver=0x556daee0, e=0x7fffd5b0) at kernel/qapplication.cpp:3640 #18 0x7669c2f8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) (receiver=0x556daee0, event=0x7fffd5b0) at kernel/qcoreapplication.cpp:1064 #19 0x766ea9bb in QTimerInfoList::activateT
[dolphin] [Bug 471556] Dolphin Search Does Not Properly Display Matching Results
https://bugs.kde.org/show_bug.cgi?id=471556 --- Comment #1 from Abystus --- Anyone had a chance to investigate this one yet? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470742] Display scale resets to auto-calculated default values under certain circumstances
https://bugs.kde.org/show_bug.cgi?id=470742 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #16 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.
[okular] [Bug 409644] [Wayland] Panning in Okular is laggy with 4K monitor
https://bugs.kde.org/show_bug.cgi?id=409644 --- Comment #12 from Yiyang Wu --- Confirm that this issue still exists on my Debian 12 Plasma-5.27 laptop. Is there any progress these days? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 471236] What plugins should I use on my tablet?
https://bugs.kde.org/show_bug.cgi?id=471236 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.
[krita] [Bug 472422] Cannot build krita; cmake 3.25.1 insists there's no install prefix when there is
https://bugs.kde.org/show_bug.cgi?id=472422 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469517] canvases will not save and keep getting deleted as if they were never made. doesn't matter what steps i take to try and prevent this krita just refuses to save my work.
https://bugs.kde.org/show_bug.cgi?id=469517 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472090] Crash When Pasting Copied Vector
https://bugs.kde.org/show_bug.cgi?id=472090 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468506] Copied content not pasting on newly-opened applications on Wayland
https://bugs.kde.org/show_bug.cgi?id=468506 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #13 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 469485] [Win11 + Angle] Moving Krita window crossing the screen border causes severe hiccups
https://bugs.kde.org/show_bug.cgi?id=469485 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470029] Save didnt create folder yet said it work
https://bugs.kde.org/show_bug.cgi?id=470029 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #7 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439776] Aqbanking/Kbanking broken in mingw builds on Windows 7
https://bugs.kde.org/show_bug.cgi?id=439776 --- Comment #12 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 463255] Window thumbnails for game windows sometimes become black squares on Wayland
https://bugs.kde.org/show_bug.cgi?id=463255 --- Comment #7 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.
[digikam] [Bug 472452] Face Recognition fails (process stuck at 0%)
https://bugs.kde.org/show_bug.cgi?id=472452 --- Comment #1 from Perry Nguyen --- First summary is my report, second summary is what's left from duplicating the previous bug. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 460570] Face Recognition fails (process stuck at 0%)
https://bugs.kde.org/show_bug.cgi?id=460570 Perry Nguyen changed: What|Removed |Added Blocks||472452 Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=472452 [Bug 472452] Face Recognition fails (process stuck at 0%) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 472452] New: Face Recognition fails (process stuck at 0%)
https://bugs.kde.org/show_bug.cgi?id=472452 Bug ID: 472452 Summary: Face Recognition fails (process stuck at 0%) Classification: Applications Product: digikam Version: 8.0.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Faces-Engine Assignee: digikam-bugs-n...@kde.org Reporter: pfngu...@hanhuy.com CC: caulier.gil...@gmail.com, digikam-bugs-n...@kde.org, egla...@gmail.com, ejec...@gmail.com, idave...@gmail.com, jsh121...@hotmail.com, metzping...@gmail.com, thomas.b...@barbthom.de, w.blanke...@t-online.de Depends on: 460570 Target Milestone: --- +++ This bug was initially created as a clone of Bug #460570 +++ 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. Launch 2. People -> Settings -> [X] Work on all processor cores 3. Scan collection for faces OBSERVED RESULT Face detection hangs at 0% and digikam must be force killed. EXPECTED RESULT Face detection scan proceeds WORKAROUND Perform a small scan with "Work on all processor cores" unchecked Perform a subsequent scan with "Work on all processor cores" checked SOFTWARE/OS VERSIONS Windows: Windows 11 macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION 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 *** Selecting People module and performing a scan on selected directories/Albums on an external drive, process remains at 0% showing only some results in Unknown People tab. External drive then switches its light off (meaning that there is no request for data from it) and process still remains at 0% on digikam. At the same time the laptop remains relatively cool meaning that there is no high demanding process running actually on it (such as face detection). Reproduced in two different by gen laptops (Lenovo X1 Carbon gen2 and gen3 respectivelly) with the same external drive used. STEPS TO REPRODUCE 1. Workflow tab: Skip images already scanned Detect faces Search in tab: 5 Albums selected Settings tab: Use YOLO v3 detection model (not selected/unchecked) Work on all processor cores (selected/checked) 2. External drive connected to laptop with those 5 Albums selected from 3. Irelevant: Settings: Miscellaneous - System - Disable hardware acceleration OpenCL (checked or unchecked with restart makes no difference) 4. OBSERVED RESULT Process is stuck with message on screen "Updating faces data base" 0% No activity on external disk Laptop remains relatively cool for such a cpu demanting process. No results in People-Unknown (or other) tab except from few findings wich might even not be from those directories selected. EXPECTED RESULT In People-Unkown tab should expect results from all the directories in a discent amount of time with the bar and percentage moving from 0% to 100%. >From there and as the Detect faces was selectted for this bug report, one could tag enough faces so for the Recognise faces to take part afterwards as a second step/scan. SOFTWARE/OS VERSIONS Windows: Windows 10 Version 2009 (x86_64) macOS: nan Linux/KDE Plasma: nan (available in About System) KDE Plasma Version: nan KDE Frameworks Version: nan Qt Version: nan ADDITIONAL INFORMATION Referenced Bugs: https://bugs.kde.org/show_bug.cgi?id=460570 [Bug 460570] Face Recognition fails (process stuck at 0%) -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409644] [Wayland] Panning in Okular is laggy with 4K monitor
https://bugs.kde.org/show_bug.cgi?id=409644 Yiyang Wu changed: What|Removed |Added CC||xgreenlandfor...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 472183] Feature Request - Instance-Specific Default Languages on Tokodon
https://bugs.kde.org/show_bug.cgi?id=472183 --- Comment #6 from Vee Satayamas --- Comment on attachment 160418 --> https://bugs.kde.org/attachment.cgi?id=160418 English instance Tokodon 23.04.3 on Tumbleweed has already showed the correct default language under the toot box. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 472183] Feature Request - Instance-Specific Default Languages on Tokodon
https://bugs.kde.org/show_bug.cgi?id=472183 --- Comment #5 from Vee Satayamas --- Comment on attachment 160417 --> https://bugs.kde.org/attachment.cgi?id=160417 Thai instance Tokodon 23.04.3 on Tumbleweed has already showed the correct default language under the toot box. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 472183] Feature Request - Instance-Specific Default Languages on Tokodon
https://bugs.kde.org/show_bug.cgi?id=472183 --- Comment #4 from Vee Satayamas --- > I think you're talking about the language option under Spellcheck right? Yes, I thought about that one. However, Tokodon 23.04.3 on Tumbleweed is exactly what I want. Because under the toot box, Tokodon shows the correct default language for both English and Thai instances. Thank you. -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 472183] Feature Request - Instance-Specific Default Languages on Tokodon
https://bugs.kde.org/show_bug.cgi?id=472183 --- Comment #3 from Vee Satayamas --- Created attachment 160418 --> https://bugs.kde.org/attachment.cgi?id=160418&action=edit English instance -- You are receiving this mail because: You are watching all bug changes.
[Tokodon] [Bug 472183] Feature Request - Instance-Specific Default Languages on Tokodon
https://bugs.kde.org/show_bug.cgi?id=472183 --- Comment #2 from Vee Satayamas --- Created attachment 160417 --> https://bugs.kde.org/attachment.cgi?id=160417&action=edit Thai instance -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 371560] Do not automatically append the Meta key to the list of shortcuts when Alt+F1 is set; instead let the actual Meta key itself be used or removed as a shortcut
https://bugs.kde.org/show_bug.cgi?id=371560 Tony changed: What|Removed |Added CC|jodr...@live.com| -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 472451] New: Bug: Perform "Toggle All Track Lock" just will not act in the selected track.
https://bugs.kde.org/show_bug.cgi?id=472451 Bug ID: 472451 Summary: Bug: Perform "Toggle All Track Lock" just will not act in the selected track. Classification: Applications Product: kdenlive Version: 23.04.2 Platform: Microsoft Windows OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: master.lee...@gmail.com Target Milestone: --- Created attachment 160416 --> https://bugs.kde.org/attachment.cgi?id=160416&action=edit Showing the issue. SUMMARY Bug: Perform "Toggle All Track Lock" just will not act in the selected track. STEPS TO REPRODUCE 1. It be in some tab with Timeline. 2. Perform the "Toggle All Track Lock" (Timeline > Tracks > Toggle All Track Lock or with default keyboard shortcut "Ctrl + Shift + L"). OBSERVED RESULT All tracks will be locks, except the track that is selected. If perform again, all tracks will unlock, but the select track will lock. EXPECTED RESULT All tracks should to be lock or unlock. SOFTWARE/OS VERSIONS Windows: Windows 10 Version 2009 (x86_64) KDE Frameworks Version: 5.107.0 Qt Version: 5.15.9 (built against 5.15.9) ADDITIONAL INFORMATION "Selected track" meaning the background fill that appear in the tracks. Realise this "background fill" changing the select track with the default keyboard shortcut, for video track, "1", "2" or for audio track, "Alt + 1", "Alt + 2". -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472090] Crash When Pasting Copied Vector
https://bugs.kde.org/show_bug.cgi?id=472090 --- Comment #2 from TheTechromancer --- > Could you pelase check if the problem is reproducible in nightly builds of > Krita? I guess the problem was fixed in the upcoming Krita 5.2... Thank you. The crash does not occur in the nightly build. However the vector shape also does not successfully paste. If this is the intended solution, I'm fine with closing this issue. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472450] kwin_core: XCB error: 152 (BadDamage)
https://bugs.kde.org/show_bug.cgi?id=472450 nekone...@protonmail.ch changed: What|Removed |Added Flags||X11+ Keywords||needs_verification -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472450] New: kwin_core: XCB error: 152 (BadDamage)
https://bugs.kde.org/show_bug.cgi?id=472450 Bug ID: 472450 Summary: kwin_core: XCB error: 152 (BadDamage) Classification: Plasma Product: kwin Version: 5.27.6 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: nekone...@protonmail.ch Target Milestone: --- SUMMARY I'm not familiar with the nature of this error but I tried looking into it: (https://www.phind.com/search?cache=29983abd-db3c-4ebb-bf46-682f4dffd59c) and it appears the error might be related to a race condition? I'm under the impression that race conditions are difficult to pin down and that I don't know if this issue will be solved because of it, but I figured it's worth mentioning) since I don't know if the KDE Plasma telemetry setting reports it. STEPS TO REPRODUCE 1. Boot into KDE Plasma from SDDM 2. Enable "session restore" from last logout in System Settings 3. Open some windows if none are open already 4. Reboot 5. Login via SDDM again 6. Check journalctl OBSERVED RESULT This error in journalctl: kwin_x11[2835]: kwin_core: XCB error: 152 (BadDamage), sequence: 25996, resource id: 16778541, major code: 143 (DAMAGE), minor code: 3 (Subtract) EXPECTED RESULT No "kwin_core" x11/XCB errors in journalctl. SOFTWARE/OS VERSIONS Linux: Arch Linux - Kernel 6.3.8-273-tkg-pds (https://github.com/frogging-family/linux-tkg) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 GPU: NVIDIA GeForce RTX 2080 Ti GPU Driver Version: 535.86.05 ADDITIONAL INFORMATION N/A -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472448] Games appear invisible when going into fullscreen on Wayland with Intel
https://bugs.kde.org/show_bug.cgi?id=472448 Zenurik changed: What|Removed |Added Summary|Games appear invisible when |Games appear invisible when |going into fullscreen on|going into fullscreen on |Wayland |Wayland with Intel -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 472449] New: Regression: pan_zoom effect with keyframes on an image produces a graphical glitch that darkens the surrounding screen
https://bugs.kde.org/show_bug.cgi?id=472449
Bug ID: 472449
Summary: Regression: pan_zoom effect with keyframes on an image
produces a graphical glitch that darkens the
surrounding screen
Classification: Applications
Product: kdenlive
Version: 23.04.3
Platform: Appimage
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Effects & Transitions
Assignee: j...@kdenlive.org
Reporter: cont...@elliotkillick.com
Target Milestone: ---
SUMMARY
This problem only happens starting with 23.x.
I've been able to fix it by changing this value from the pan_zoom filter:
00:00:00.000=0x;00:00:03.100=0x
TO
00:00:00.000=0x
This also works (and is the value used in 22.x Kdenlive):
0=/home/user/Videos/0x
I found this out by diffing the files produced by 22.x vs 23.x where the bug
occurred until I changed the exact line that fixed the issue.
STEPS TO REPRODUCE
1. Create new 23.x project
2. Add video in V1 track
3. Add image (I test PNG and WEBP, this bug occurs with both) in V2 track
4. Add pan_zoom ("Position and Zoom") effect to image
5. Add keyframe to image that just makes it move (for example)
6. Save project
7. Re-open and observe the bug (rendering even without re-opening will also
allow you to observe it)
OBSERVED RESULT
Graphical glitch causes screen to be darkened around image.
EXPECTED RESULT
No graphical glitch.
SOFTWARE/OS VERSIONS
AppImage, tested on Fedora 38 and Debian 11VM
ADDITIONAL INFORMATION
A project converted from 22.x to 23.x will not see the issue at first. It's
only when you add a new pan_zoom effect with keyframes on an image that you
will see the graphical glitch on that new element.
--
You are receiving this mail because:
You are watching all bug changes.
[kwin] [Bug 472448] New: Games appear invisible when going into fullscreen on Wayland
https://bugs.kde.org/show_bug.cgi?id=472448 Bug ID: 472448 Summary: Games appear invisible when going into fullscreen on Wayland Classification: Plasma Product: kwin Version: 5.27.6 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: alisson@outlook.com Target Milestone: --- SUMMARY Under Wayland with Intel graphics, whenever I try to enable fullscreen in a game the window just becomes invisible and unresponsive. Tried with Minecraft (OpenGL, native) and Celeste (DXVK/OpenGL, wine) with the same results. STEPS TO REPRODUCE 1. Open any game that runs under XWayland (via Steam is preferred) 2. Under the game's options, enable fullscreen. OBSERVED RESULT Game window will become invisible (sound and keyboard commands still work) EXPECTED RESULT Enabling fullscreen from a game should display the game as exclusive fullscreen as expected. SOFTWARE/OS VERSIONS Operating System: Solus 4.4 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.9 Kernel Version: 6.3.12-241.current (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-7200U CPU @ 2.50GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 620 ADDITIONAL INFORMATION - Custom font DPI settings are used - Changing anything under Compositor settings has no effect - I have not tried / know of other types of applications that would have the same issue -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 472446] Wayland randomly flickering
https://bugs.kde.org/show_bug.cgi?id=472446 --- Comment #1 from Arthur Helsftein Fragoso --- At one point I got the Application Launcher menu to glitch together with the cursor: https://youtu.be/zSVPNLz0xms This glitch in the menu is not happening in the moment, but maybe they are related. I also noticed the menu got a somewhat transparent effect, as it normally has a solid gray background, and as we see in the video, it was a light gray. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 466320] kpipewire_logging: Window not available PipeWireSourceItem_QML_1025
https://bugs.kde.org/show_bug.cgi?id=466320 Brandon Cooper changed: What|Removed |Added CC||brandon.coo...@disroot.org -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 472447] Files cannot keep up with the mouse while dragging on the desktop or in Dolphin.
https://bugs.kde.org/show_bug.cgi?id=472447 --- Comment #1 from tjw12...@126.com --- Created attachment 160415 --> https://bugs.kde.org/attachment.cgi?id=160415&action=edit OBSERVED RESULT -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 472447] New: Files cannot keep up with the mouse while dragging on the desktop or in Dolphin.
https://bugs.kde.org/show_bug.cgi?id=472447 Bug ID: 472447 Summary: Files cannot keep up with the mouse while dragging on the desktop or in Dolphin. Classification: Applications Product: dolphin Version: 23.04.3 Platform: Kubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: general Assignee: dolphin-bugs-n...@kde.org Reporter: tjw12...@126.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Files cannot keep up with the mouse while dragging on the desktop or in Dolphin. STEPS TO REPRODUCE 1. Open Dolphin or Desktop. 2. Attempt to drag files. OBSERVED RESULT Files cannot keep up with the mouse. EXPECTED RESULT The files keep up with the mouse. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Kubuntu 23.04 KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 472446] Wayland randomly flickering
https://bugs.kde.org/show_bug.cgi?id=472446 Arthur Helsftein Fragoso changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 472446] New: Wayland randomly flickering
https://bugs.kde.org/show_bug.cgi?id=472446 Bug ID: 472446 Summary: Wayland randomly flickering Classification: I don't know Product: kde Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: art...@life.net.br Target Milestone: --- SUMMARY I decided to give Wayland a try today, but it is still too glitchy. The easiest way I can reproduce this myself, is by being away from the PC for about 30 seconds, not using the mouse or keyboard. When I move it again, the current window flickers showing what is in the background. Example: https://youtu.be/gRuS6vY9OY0 (recorded in 0.25 speed) But even if I don't step away and keep just using it normally, it just randomly flicker here and there. I'm on Manjaro and installed it using the command: sudo pacman -S wayland plasma-wayland-session It's a Nvidia GPU and drivers. Just let me know any more information I could provide. SOFTWARE/OS VERSIONS uname -a Linux Mozart 5.15.120-1-MANJARO #1 SMP PREEMPT Wed Jul 5 21:45:37 UTC 2023 x86_64 GNU/Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION pacman -Q |grep -e "kde\|qt\|wayland\|nvidia" appstream-qt 0.16.2-1 bluez-qt 5.108.0-1 colord-kde 23.04.3-1 egl-wayland 2:1.1.12-1 kde-cli-tools 5.27.6-1 kde-gtk-config 5.27.6-1 kdeclarative 5.108.0-1 kdeconnect 23.04.3-1 kdecoration 5.27.6-1 kded 5.108.0-1 kdegraphics-mobipocket 23.04.3-1 kdegraphics-thumbnailers 23.04.3-1 kdelibs4support 5.108.0-1 kdenetwork-filesharing 23.04.3-1 kdenlive 23.04.3-1 kdeplasma-addons 5.27.6-2 kdeplasma-applets-fokus 1.5.5-1 kdesu 5.108.0-1 kwayland 5.108.0-1 kwayland-integration 5.27.6-1 layer-shell-qt 5.27.6-1 lib32-nvidia-utils 535.54.03-1 lib32-wayland 1.22.0-1 libaccounts-qt 1.16-3 libblockdev 2.28-4 libdbusmenu-qt5 0.9.3+16.04.20160218-6 linux515-nvidia 535.54.03-5 manjaro-kde-settings 20230529-1 mgba-qt 0.10.2-1 mhwd-nvidia 535.54.03-1 mhwd-nvidia-390xx 390.157-7 mhwd-nvidia-470xx 470.199.02-2 modemmanager-qt 5.108.0-1 networkmanager-qt 5.108.0-1 nvidia-utils 535.54.03-1 packagekit-qt5 1.1.1-1 phonon-qt5 4.11.1-3 phonon-qt5-gstreamer 4.10.0-4 plasma-wayland-session 5.27.6-2 polkit-kde-agent 5.27.6-1 polkit-qt5 0.114.0-1 poppler-qt5 23.07.0-1 pulseaudio-qt 1.3-1 python-pyqt5 5.15.9-2 python-pyqt5-sip 12.12.1-2 python-pyqt5-webengine 5.15.6-2 python-pyqt6 6.5.1-1 python-pyqt6-sip 13.5.1-2 python-pyqt6-webengine 6.5.0-2 python-qtpy 2.3.1-2 python-sphinxcontrib-qthelp 1.0.3-11 qca-qt5 2.3.6-2 qgpgme-qt5 1.21.0-1 qscintilla-qt5 2.14.1-1 qt5-base 5.15.10+kde+r130-1 qt5-declarative 5.15.10+kde+r26-1 qt5-doc 5.15.10-1 qt5-graphicaleffects 5.15.10-1 qt5-imageformats 5.15.10+kde+r9-1 qt5-location 5.15.10+kde+r4-2 qt5-mqtt 5.15.2-10 qt5-multimedia 5.15.10+kde+r3-1 qt5-networkauth 5.15.10-1 qt5-quickcontrols 5.15.10-1 qt5-quickcontrols2 5.15.10+kde+r6-1 qt5-sensors 5.15.10-1 qt5-serialport 5.15.10-1 qt5-speech 5.15.10+kde+r1-1 qt5-svg 5.15.10+kde+r8-1 qt5-tools 5.15.10+kde+r3-1 qt5-translations 5.15.10-1 qt5-virtualkeyboard 5.15.10-1 qt5-wayland 5.15.10+kde+r51-1 qt5-webchannel 5.15.10+kde+r3-1 qt5-webengine 5.15.14-4 qt5-webkit 5.212.0alpha4-16 qt5-websockets 5.15.10+kde+r2-1 qt5-x11extras 5.15.10-1 qt5-xmlpatterns 5.15.10-1 qt6-5compat 6.5.1-2 qt6-base 6.5.1-5 qt6-declarative 6.5.1-2 qt6-imageformats 6.5.1-1 qt6-multimedia 6.5.1-1 qt6-multimedia-ffmpeg 6.5.1-1 qt6-positioning 6.5.1-1 qt6-svg 6.5.1-1 qt6-translations 6.5.1-1 qt6-wayland 6.5.1-1 qt6-webchannel 6.5.1-1 qt6-webengine 6.5.1-2 qt6-websockets 6.5.1-1 qtkeychain-qt5 0.14.1-1 qtox 1.17.6-2 qtractor 0.9.34-2 quazip-qt5 1.4-1 qxlsx-qt5 1.4.6-1 wayland 1.22.0-1 wayland-protocols 1.31-1 wayland-utils 1.2.0-1 wireshark-qt 4.0.7-1 xdg-desktop-portal-kde 5.27.6-1 xorg-xwayland 23.1.2-1 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 472422] Cannot build krita; cmake 3.25.1 insists there's no install prefix when there is
https://bugs.kde.org/show_bug.cgi?id=472422 --- Comment #2 from David --- Created attachment 160414 --> https://bugs.kde.org/attachment.cgi?id=160414&action=edit CMakeOutput.log Here you go, using a fresh git clone. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472445] New: Persistent blackscreen on X11 and Wayland after changing screen resolution
https://bugs.kde.org/show_bug.cgi?id=472445 Bug ID: 472445 Summary: Persistent blackscreen on X11 and Wayland after changing screen resolution Classification: Plasma Product: kwin Version: 5.27.6 Platform: openSUSE OS: Linux Status: REPORTED Severity: major Priority: NOR Component: core Assignee: kwin-bugs-n...@kde.org Reporter: holdenrf2...@gmail.com Target Milestone: --- SUMMARY Was playing around with a few things with theming over the past day or two on my work laptop, which is a Dell Inspiron 16 5625 with AMD 5825U CPU/Radeon graphics on OpenSUSE Tumbleweed kernel 6.4.3-1. Had changed a number of things and could be related to any of these, but what kicked off the blackscreen was changing the resolution from the default 1920x1200 to 1920x1080. Upon doing this, my screen instantly went black and it was clear things were...running fine but just...not displaying in the right place. Changing to ttyX worked fine and I could log in, but even on restarting sddm, reloading to multi-user.target, graphical.target, etc. and restarting sddm, running "startx," etc. etc. etc. failed. Reboot would bring up sddm login screen just fine, but trying to login to either Plasma X11 or Plasma Wayland would lead to the same black screen. It's notable to mention that IceWM which is included by default in OpenSUSE TW would open fine. At least if it was the first option chosen after reboot. Additionally, systemctl wasn't reporting any failed services or units that I could tell... Could always change to ttyX using standard keystrokes but no matter what I did, nothing in my standard "toolkit" would get it to restart normally until I physically plugged in an external monitor. Even physically changing ~/.local/share/kscreen/output/relevantscreen values back to 1920x1200 didn't seem to work until I finally plugged in the external monitor, upon which everything came back up and appeared to display just fine. It's also notable that I had been running another VM of nixOS with KDE plasma using kvm/qemu virtualization in virt-manager at the time, using the modular systemd services and with a network bridge attached. I initially tried lowering the resolution because virt-manager kept trying to display the VM window too large and that appeared to be on the host side of things rather than the VM side (i.e. windowing of the virt-manager screen on my host OS was defaulting too large and going offscreen). Was really just playing around testing a few things and not expecting something like this to cause such a serious crash. Anyways, I'm not sure if the crash logs below are fully related but I've been needing to get more involved in open source projects and KDE is one of my favorites. :) I can try to reproduce later if information supplied is insufficient, but as this is my work laptop I'm more hesitant to break it... This could also be related to some of the other things I was testing, so I'm happy to provide more information if needed. Was kinda doing a lot on this laptop the past few days, so it could be more of a "me" problem than a bug others would hit. Moved from a dual boot setup with windows/opensuse TW and was hoping to use my current windows install (now in a USB-C NVME adapter) sandboxed in a VM for the very rare occasion I would need it for testing future windows builds of software for work. Also backed up my previous home folder from the dual-boot setup (same setup with OpenSUSE TW/Plasma) in a sub-subdirectory within my new ~/Desktop so I considered the case maybe some config files were getting sourced incorrectly, but I wouldn't think that would be the case... *** 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 (Have not tried since fixing, but I can later on if needed) 1. ... 2. Change screen resolution from default 1920x1200 to 1920x1080 3. Blackscreen? 4. Annoyance OBSERVED RESULT EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: Opensuse tumbleweed, kernel 6.4.3.1-default (64 bit) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION holden@tumble-dell:~$ sudo coredumpctl gdb 3309 PID: 3309 (kwin_wayland) UID: 1000 (holden) GID: 1000 (holden) Signal: 11 (SEGV) Timestamp: Thu 2023-07-20 17:22:56 EDT (1h 36min ago) Command Line: /usr/bin/kwin_wayland --wayland-fd 7 --socket wayland-0 --xwayland-fd 8 --xwayland-fd 9 --xwayland-display :1 --xwayland-xauthority /run/user/1000/xauth_VnHRnI --xwayland Executable: /usr/bin/kwin_wayland Control Group: /user.slice/user-1000.slice/user@1000.service/session.slice/plasma-kwin_wayland.service Unit: user@1000.service User Unit: plasma-
[kdenetwork-filesharing] [Bug 463067] The plugin doesn't see already created Samba users when trying to create a share
https://bugs.kde.org/show_bug.cgi?id=463067
wokim changed:
What|Removed |Added
CC||mequer...@gmail.com
--- Comment #7 from wokim ---
I'm having the same bug on Arch Linux. Only on my laptop though, for some
reason it works fine on my desktop.
And I know this isn't a proper fix, but just adding "true || " to the first
line of User::resolve() works:
> if (true || !qobject_cast(parent())->canManageSamba() ||
> m_name == everyoneUserName) {
--
You are receiving this mail because:
You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 472443] Currency rate change dont update
https://bugs.kde.org/show_bug.cgi?id=472443 Jack changed: What|Removed |Added Status|REPORTED|RESOLVED CC||ostroffjh@users.sourceforge ||.net Resolution|--- |DUPLICATE --- Comment #1 from Jack --- Please don't open a new bug to report to report a fix, especially where there is already a bug open, and the breakage is caused by a source we don't control. This has also been addresses (with a slightly different change to the PRICE regex) on Discuss, which is a better place to report such updates, or else one of the mailing lists. Anyway, thanks for confirming that editing the regex fixes the problem. *** This bug has been marked as a duplicate of bug 472423 *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 472423] Currency update fails for CAD/USD and USD/CAD
https://bugs.kde.org/show_bug.cgi?id=472423 Jack changed: What|Removed |Added CC||jfia...@tiscali.it --- Comment #5 from Jack --- *** Bug 472443 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 472423] Currency update fails for CAD/USD and USD/CAD
https://bugs.kde.org/show_bug.cgi?id=472423 Jack changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME CC||ostroffjh@users.sourceforge ||.net -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 455012] With a large number of tabs open, the browser starts slowly
https://bugs.kde.org/show_bug.cgi?id=455012 --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/network/falkon/-/merge_requests/58 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 472423] Currency update fails for CAD/USD and USD/CAD
https://bugs.kde.org/show_bug.cgi?id=472423 --- Comment #4 from Pete --- Jack, The change worked fine. Please close this bug. Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415599] Add date to help DNN face recognition for baby/kid/adult distinction
https://bugs.kde.org/show_bug.cgi?id=415599 --- Comment #5 from Craig --- (In reply to Alexandre Belz from comment #4) > Hi guys, > > i'm working in a company that is now using A.I. and many parameters seem to > be potentially added to the "big data" in which the -customized- AI engine > works and determine statistical results. > More than ever, i do believe that adding *additionnal metadata* such as > "date taken" to au updated DNN module (or any other picture oriented AI) > should (must?) help to improve the quality of the estimation model, and > thus, the face recognition. > In other words, as a face is not static, and will, fore sure, evolve with > years, how does the AI enginee manages this evolution ? > The above comments would deserve to be sent to the DNN team, i think, and > recommend. With the exception of very young children, most face recognition software, and indeed people that are good at recognising faces, use parameters that don't change significantly over a persons life. These parameters are primarily ratios of distances between the main features such as the distance between the eyes and the mouth or eyes and the end of the nose. Less important parameters are also used such as the distance between the edge of the chin and the sides of the face inline with the eyes. There are many of these parameters that are used and most change little as they are based around the skull, which normally doesn't change significantly over a person's lifetime. Now using NN, these specific ratios many not be specifically programmed, but they form the basis of the identification process. After reading about this topic, including how people who are considered super recognisers perform the task so well, I realised that I personally have flaws in how I recognise people. I found that I unknowingly rely heavily on people's hair or hair style, which of course is easily changed in length, coverage, shape and colour. Clear not a good parameter to use for identification. Other parameters the people often rely on that are poor parameters to use include skin texture, skin colour and even the thickness of the skin. These parameters all change over a person's life, but they are also easily changed due to lighting, humidity, temperature and makeup. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472444] force keyboard layout for nested kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=472444 Bug Janitor Service changed: What|Removed |Added Keywords||qt6 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[keditbookmarks] [Bug 443650] Bookmarks for folders have no icons
https://bugs.kde.org/show_bug.cgi?id=443650 --- Comment #1 from tlazolteotlak...@gmail.com --- If you are using the default Breeze icon Icons it will show the Breeze icon instead of the broken icon image. Unfortunately, even with the Breeze icon scheme enabled you can't use non-Breeze icons for the bookmarks, and I find the Breeze icons washed out and hard to distinguish from one another, so I'd just as soon have the 'busted icon' icon. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 472423] Currency update fails for CAD/USD and USD/CAD
https://bugs.kde.org/show_bug.cgi?id=472423 --- Comment #3 from Jack --- Sorry. https://bugs.kde.org/show_bug.cgi?id=472443 is a newly filed bug for the same issue (I think) which suggests I have solved it changing 1\s[^=]+\s=\s([^\s]+) with 1\s[^=]+\s=\s([^\s]+) If that works for you, I'll close that bug as a duplicate of this one, and close this one as fixed. To make that change, invoke the menu Settings/Configure KMyMoney..., select Online Quotes on the left, then KMyMoney Currency on the right. The edit is just removing two characters from the regular expression in the Price text box. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 470595] filelight crashes with segfault
https://bugs.kde.org/show_bug.cgi?id=470595 Harald Sitter changed: What|Removed |Added Resolution|--- |WORKSFORME Status|REPORTED|RESOLVED CC||sit...@kde.org --- Comment #2 from Harald Sitter --- Unfortunately the backtrace seems rather useless. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 471328] Add checkbox to disable sidebar
https://bugs.kde.org/show_bug.cgi?id=471328 Harald Sitter changed: What|Removed |Added CC||sit...@kde.org Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from Harald Sitter --- There are no plans to add such an option. -- You are receiving this mail because: You are watching all bug changes.
[lokalize] [Bug 471802] Crash after editing a plural
https://bugs.kde.org/show_bug.cgi?id=471802 --- Comment #19 from Frederik Schwarzer --- If you download the old file and open it in Lokalize, can you reproduce this with it?? -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 471091] Filelight analyses home folder, then crashes
https://bugs.kde.org/show_bug.cgi?id=471091 Harald Sitter changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM CC||sit...@kde.org --- Comment #1 from Harald Sitter --- Looks like a bug in the nvidia driver. -- You are receiving this mail because: You are watching all bug changes.
[filelight] [Bug 470565] Crash after try to scan sftp path
https://bugs.kde.org/show_bug.cgi?id=470565 Harald Sitter changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UNMAINTAINED CC||sit...@kde.org --- Comment #1 from Harald Sitter --- 22.12 is unfortunately no longer supported. Best talk to your distro. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 472423] Currency update fails for CAD/USD and USD/CAD
https://bugs.kde.org/show_bug.cgi?id=472423 --- Comment #2 from Pete --- (In reply to Jack from comment #1) > please look at bug 472423 and see if that solution fixes if for you also. Jack, please clarify your comment. What should I look at? Thanks. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 415599] Add date to help DNN face recognition for baby/kid/adult distinction
https://bugs.kde.org/show_bug.cgi?id=415599 --- Comment #4 from Alexandre Belz --- Hi guys, i'm working in a company that is now using A.I. and many parameters seem to be potentially added to the "big data" in which the -customized- AI engine works and determine statistical results. More than ever, i do believe that adding *additionnal metadata* such as "date taken" to au updated DNN module (or any other picture oriented AI) should (must?) help to improve the quality of the estimation model, and thus, the face recognition. In other words, as a face is not static, and will, fore sure, evolve with years, how does the AI enginee manages this evolution ? The above comments would deserve to be sent to the DNN team, i think, and recommend. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 472444] New: force keyboard layout for nested kwin_wayland
https://bugs.kde.org/show_bug.cgi?id=472444 Bug ID: 472444 Summary: force keyboard layout for nested kwin_wayland Classification: Plasma Product: kwin Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: sit...@kde.org Target Milestone: --- SUMMARY In our selenium tech we use a nested kwin_wayland and send keyboard events through the fakeinput protocol. It'd be lovely if we could force the nested kwin to always use a specific XKB Rules + Model + Layouts + Variants + Options instead of using the ones from the config. Otherwise it's impossible for the outside to generate reliable keycodes for the protocol because we don't know what layout is being used nor which modifiers are set up. STEPS TO REPRODUCE 1. systemsettings kcm_keyboard 2. go to layouts tab 3. add german (austria) as first layout 4. add english (US) as second layout 5. kwin_wayland kwrite OBSERVED RESULT The nested kwin uses the austrian layout and there appears to be no way to force it to use US. EXPECTED RESULT Ability to force keyboard layout somehow. ENV vars might be the most in line with xkbcommon SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.27.80 KDE Frameworks Version: 5.240.0 Qt Version: 6.6.0 Kernel Version: 5.19.0-46-generic (64-bit) Graphics Platform: offscreen Processors: 12 × AMD Ryzen 5 3600X 6-Core Processor Memory: 31.2 GiB of RAM Graphics Processor: AMD Radeon RX 5700 XT ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 472423] Currency update fails for CAD/USD and USD/CAD
https://bugs.kde.org/show_bug.cgi?id=472423 Jack changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #1 from Jack --- please look at bug 472423 and see if that solution fixes if for you also. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 471856] With Windows plugin enables, after creating a new instance of Firefox using KRunner, trying to create another one focuses the new instance instead
https://bugs.kde.org/show_bug.cgi?id=471856 Nate Graham changed: What|Removed |Added Component|general |windows Summary|After creating a new|With Windows plugin |instance of Firefox using |enables, after creating a |KRunner, trying to create |new instance of Firefox |another one focuses the new |using KRunner, trying to |instance instead|create another one focuses ||the new instance instead Version|unspecified |5.27.6 Keywords|qt6 | --- Comment #3 from Nate Graham --- Thanks! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469354] Ctrl scroll zoom direction is inverted in dolphin detail view
https://bugs.kde.org/show_bug.cgi?id=469354 Evert Vorster changed: What|Removed |Added CC||evors...@protonmail.com --- Comment #2 from Evert Vorster --- Can confirm, Ctrl + Scroll does funky things in Dolphin. For me, it appears that it only zooms one way, no matter if you scroll up or down on the mouse wheel. I'll try the pressing ctrl twice trick. I have multiple panels open in Dolphin, and like Icon View with splits, and I zoom in and out often, and so this bug is a little annoying. System information: ``` Operating System: Arch Linux KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 Kernel Version: 6.4.4-arch1-1 (64-bit) Graphics Platform: Wayland Processors: 8 × AMD Ryzen 7 4700U with Radeon Graphics Memory: 36.9 GiB of RAM Graphics Processor: AMD Radeon Graphics Manufacturer: LENOVO Product Name: 20T8001JUS System Version: ThinkPad E15 Gen 2 ``` -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 472443] New: Currency rate change dont update
https://bugs.kde.org/show_bug.cgi?id=472443 Bug ID: 472443 Summary: Currency rate change dont update Classification: Applications Product: kmymoney Version: 5.1.3 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: website Assignee: kmymoney-de...@kde.org Reporter: jfia...@tiscali.it Target Milestone: --- SUMMARY Since 18.7.2023 the rate change dont update online I have solved it changing 1\s[^=]+\s=\s([^\s]+) with 1\s[^=]+\s=\s([^\s]+) I suppose that fx-rate.net page have been modified -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 472442] New: Choosing sensors is broken, very few sensors are offered
https://bugs.kde.org/show_bug.cgi?id=472442 Bug ID: 472442 Summary: Choosing sensors is broken, very few sensors are offered Classification: Applications Product: plasma-systemmonitor Version: 5.27.6 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: ksysguard-b...@kde.org Reporter: m...@patrick-nagel.net CC: ahiems...@heimr.nl, plasma-b...@kde.org Target Milestone: --- SUMMARY When configuring a sensor widget, the menu that is shown when clicking "Click to select a sensor..." is missing lots of content. Example: I only get offered Power and Disks. Under Disks I only have a single item "3.6 TiB Internal Drive (dm-0)" and under that I only have a single item "... Read Rate (B/s)". Even tough in an existing widget I have a graph of another drive (dm-1) - it should have been shown as well, amongst many other things. STEPS TO REPRODUCE 1. Open System Monitor 2. Add a new page 3. Click on System Monitor Sensor 4. In the right pane, click on "Click to select a sensor..." OBSERVED RESULT Very few entries in the menu, lots of content missing EXPECTED RESULT The usual content to choose from SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 23.10 / 6.3.0-7-generic (64-bit) (available in About System) KDE Plasma Version: 5.27.6 KDE Frameworks Version: 5.108.0 Qt Version: 5.15.10 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 471856] After creating a new instance of Firefox using KRunner, trying to create another one focuses the new instance instead
https://bugs.kde.org/show_bug.cgi?id=471856 --- Comment #2 from publiclyvisibleem...@gmail.com --- (In reply to Nate Graham from comment #1) > Can reproduce with Firefox, but not Dolphin. > > Is this a regression from Plasma 5? At least for me this happens in Plasma 5 as well. The way I get around it in both 5 & 6 is to disable the Plasma Search Windows plugin. I lose the ability to select open windows by name via krunner, but I have alt-tab for dealing with open windows and if I can only have one of keyboard title selection for open windows, (which is cute, but would be a new addition to my standard workflow that I've never really had, so I certainly don't really rely on it at all at this point) vs easily launching new instances, (a bread and butter workflow item for me for decades) the launching new instances is way more important, so disabling the Windows plugin works fine. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 472441] New: Manually sorted windows are resetted when opening the launcher, but just once
https://bugs.kde.org/show_bug.cgi?id=472441 Bug ID: 472441 Summary: Manually sorted windows are resetted when opening the launcher, but just once Classification: Plasma Product: plasmashell Version: 5.27.5 Platform: Debian unstable OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: plasma-b...@kde.org Reporter: m...@familie-heinz.name Target Milestone: 1.0 SUMMARY When starting plasma there are a few programs that are started automatically, like Firefox with several windows. Then I drag those windows around in the task manager bar. If I then open the launcher the window order in the task manager will get resetted to what it was like before. I can then rearrange them again. Opening the launcher now will not change the order anymore. The sorting of the windows is set to manual. STEPS TO REPRODUCE 1. Start plasma 2. Have some windows opened by some programs 3. Move the windows around in the task bar 4. Open the launcher (I do this with the Meta key) OBSERVED RESULT The windows should be resetted to their initial order. EXPECTED RESULT The window order doesn't change. 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.
[kwin] [Bug 471950] Distorted windows contents on recovering from sleep / hibernate
https://bugs.kde.org/show_bug.cgi?id=471950 --- Comment #4 from publiclyvisibleem...@gmail.com --- (In reply to Nate Graham from comment #3) > Does it happen on Wayland too? Only saw it happen that one time in an X11 session, so afraid I can't say. That being said, I have a pretty awful time getting my laptop to come back from sleep / hibernate without needing to be force-shutdown and restarted, (i.e. I'd say I have to force-shutdown probably 95+ times out of a 100) so perhaps this was just an artifact of that and for other folks who don't have nearly as bad a time resuming this wouldn't happen, so I guess go ahead and close this for now unless someone else is getting this as well. -- You are receiving this mail because: You are watching all bug changes.
