[digikam] [Bug 421023] Face tagging quirky in digiKam 7.0.0-beta3
https://bugs.kde.org/show_bug.cgi?id=421023 --- Comment #8 from Maik Qualmann --- Git commit 1e88b3a88c20492705de121c13d06fce4b312262 by Maik Qualmann. Committed on 12/05/2020 at 05:56. Pushed by mqualmann into branch 'master'. disable updating the tag list for a test M +2-2core/libs/database/coredb/coredb.cpp https://invent.kde.org/kde/digikam/commit/1e88b3a88c20492705de121c13d06fce4b312262 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 421232] [Wayland] Fullscreen in mpv cannot be enabled by double-clicking
https://bugs.kde.org/show_bug.cgi?id=421232 Vlad Zahorodnii changed: What|Removed |Added Flags||Wayland+, X11- -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 420727] digiKam-Window and all Sub-Windows are enlarged too much
https://bugs.kde.org/show_bug.cgi?id=420727 --- Comment #33 from Maik Qualmann --- I tested the setting of the environment variable again under 2 different Windows installations, it works perfectly. Maik -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421390] New: KDE plasma crashed
https://bugs.kde.org/show_bug.cgi?id=421390 Bug ID: 421390 Summary: KDE plasma crashed Product: plasmashell Version: 5.18.5 Platform: unspecified OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: f.schrei...@procar.de CC: plasma-b...@kde.org Target Milestone: 1.0 Application: plasmashell (5.18.5) Qt Version: 5.14.2 Frameworks Version: 5.70.0 Operating System: Linux 5.3.0-51-generic x86_64 Windowing system: X11 Distribution: KDE neon User Edition 5.18 -- Information about the crash: - What I was doing when the application crashed: The error message was showen. when i confirm my login. I get a black backround, no shortcuts, no taskbar -- Backtrace: Application: Plasma (plasmashell), signal: Segmentation fault Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f54bf4271c0 (LWP 1902))] Thread 11 (Thread 0x7f546210d700 (LWP 2267)): #0 0x7f54b5b659f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x564aa3e9e874) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x564aa3e9e820, cond=0x564aa3e9e848) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x564aa3e9e848, mutex=0x564aa3e9e820) at pthread_cond_wait.c:655 #3 0x7f54b8ee31db in QWaitConditionPrivate::wait (deadline=..., this=0x564aa3e9e820) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x564aa433f4b0, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f54b8ee3359 in QWaitCondition::wait (this=this@entry=0x564aa433f4b8, mutex=mutex@entry=0x564aa433f4b0, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7f54bcfe6233 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x564aa433f4a8) at scenegraph/qsgthreadedrenderloop.cpp:255 #7 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x564aa433f410) at scenegraph/qsgthreadedrenderloop.cpp:905 #8 0x7f54bcfe6691 in QSGRenderThread::run (this=0x564aa433f410) at scenegraph/qsgthreadedrenderloop.cpp:1000 #9 0x7f54b8edcc2c in QThreadPrivate::start (arg=0x564aa433f410) at thread/qthread_unix.cpp:342 #10 0x7f54b5b5f6db in start_thread (arg=0x7f546210d700) at pthread_create.c:463 #11 0x7f54b87d188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 10 (Thread 0x7f546310f700 (LWP 2264)): #0 0x7f54b5b659f3 in futex_wait_cancelable (private=, expected=0, futex_word=0x564aa0cf80b0) at ../sysdeps/unix/sysv/linux/futex-internal.h:88 #1 __pthread_cond_wait_common (abstime=0x0, mutex=0x564aa0cf8060, cond=0x564aa0cf8088) at pthread_cond_wait.c:502 #2 __pthread_cond_wait (cond=0x564aa0cf8088, mutex=0x564aa0cf8060) at pthread_cond_wait.c:655 #3 0x7f54b8ee31db in QWaitConditionPrivate::wait (deadline=..., this=0x564aa0cf8060) at thread/qwaitcondition_unix.cpp:146 #4 QWaitCondition::wait (this=, mutex=0x564a9e8daf60, deadline=...) at thread/qwaitcondition_unix.cpp:225 #5 0x7f54b8ee3359 in QWaitCondition::wait (this=this@entry=0x564a9e8daf68, mutex=mutex@entry=0x564a9e8daf60, time=time@entry=18446744073709551615) at thread/qwaitcondition_unix.cpp:208 #6 0x7f54bcfe6233 in QSGRenderThreadEventQueue::takeEvent (wait=true, this=0x564a9e8daf58) at scenegraph/qsgthreadedrenderloop.cpp:255 #7 QSGRenderThread::processEventsAndWaitForMore (this=this@entry=0x564a9e8daec0) at scenegraph/qsgthreadedrenderloop.cpp:905 #8 0x7f54bcfe6691 in QSGRenderThread::run (this=0x564a9e8daec0) at scenegraph/qsgthreadedrenderloop.cpp:1000 #9 0x7f54b8edcc2c in QThreadPrivate::start (arg=0x564a9e8daec0) at thread/qthread_unix.cpp:342 #10 0x7f54b5b5f6db in start_thread (arg=0x7f546310f700) at pthread_create.c:463 #11 0x7f54b87d188f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7f546a074700 (LWP 2262)): #0 0x7f54b268f629 in g_mutex_lock () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x7f54b2648fec in g_main_context_check () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f54b2649570 in ?? () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f54b26496dc in g_main_context_iteration () from /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7f54b912b7cb in QEventDispatcherGlib::processEvents (this=0x7f545c000b20, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #5 0x7f54b90cad2a in QEventLoop::exec (this=this@entry=0x7f546a073da0, flags=..., flags@entry=...) at kernel/qeventloop.cpp:225 #6 0x7f54b8edb757 in QThread::exec (this=) at thread/qthread.cpp:536 #7 0x7f54b8edcc2c in QThreadPrivate::start (arg=0x564aa0b7e200) at thread/qthread_unix.cpp:342 #8 0x7f54b5b5f6db in start_thread (arg=0x7f546a074700) at
[kwin] [Bug 421202] Minimize button not shown, Resize not possible with Libre Office
https://bugs.kde.org/show_bug.cgi?id=421202 --- Comment #6 from Vlad Zahorodnii --- (In reply to Michael Josenhans from comment #5) > I have started "xprop" on the command line and then pressed a key on the > LibreOffile Writer window. > > Nothing happens. If you click the libreoffice writer window, xprop will print a lot of stuff to the terminal. Could you please post the output of xprop here? -- You are receiving this mail because: You are watching all bug changes.
[KBibTeX] [Bug 421389] New: When View Document fails, no error is displayed
https://bugs.kde.org/show_bug.cgi?id=421389 Bug ID: 421389 Summary: When View Document fails, no error is displayed Product: KBibTeX Version: 0.9.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Loading/saving files Assignee: fisc...@unix-ag.uni-kl.de Reporter: glyphi...@gmail.com Target Milestone: --- SUMMARY When an element has an incorrect file link and View Document fails, it does so silently, with no error in the GUI and no message printed on the command line. STEPS TO REPRODUCE 1. On the External tab, add or edit a file link so it's not correct 2. Trigger View Document OBSERVED RESULT Nothing happens. EXPECTED RESULT Error message is displayed in GUI and/or command line SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: 5.67.0 Qt Version: 5.14.1 ADDITIONAL INFORMATION I think this behavior changed recently? I seem to remember there used to be a popup when a linked file was no longer present. Submitting a vote to bring it back. (At least when there actually is a file link -- a "no response" seems appropriate if nothing's linked.) -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421387] Camera Leica V-Lux (Typ 114) not supported
https://bugs.kde.org/show_bug.cgi?id=421387 Maik Qualmann changed: What|Removed |Added Platform|Other |Ubuntu Packages Component|Setup-Cameras |Preview-RAW -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421387] Camera Leica V-Lux (Typ 114) not supported
https://bugs.kde.org/show_bug.cgi?id=421387 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.0.0 Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Maik Qualmann --- The Type 115 does not seem to exist. With digiKam-7.0.0-RC and a test RAW from the web of the Leica V-Lux (Type 114) everything works perfectly. I close the bug. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdesrc-build] [Bug 421388] New: plasma-workspace, plasma-desktop, plasma-vault fail to configure for build
https://bugs.kde.org/show_bug.cgi?id=421388 Bug ID: 421388 Summary: plasma-workspace, plasma-desktop, plasma-vault fail to configure for build Product: kdesrc-build Version: Git Platform: Neon Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: general Assignee: mp...@kde.org Reporter: msdobre...@gmail.com Target Milestone: --- Created attachment 128383 --> https://bugs.kde.org/attachment.cgi?id=128383=edit plasma-desktop error log SUMMARY STEPS TO REPRODUCE I follow the kdesrc-build guide, I try to build all by issuing: kdesrc-build plasma-desktop plasma-workspace plasma-framework plasma-nm plasma-pa plasma-thunderbolt plasma-vault plasma-workspace-wallpapers kdeplasma-addons kwin systemsettings kscreen breeze discover kinfocenter --include-dependencies --refresh-build It fails due to the following error type: CMake Error at /home/myuser/kde/usr/lib/x86_64-linux-gnu/cmake/KF5SysGuard/KF5SysGuardConfig.cmake:34 (add_library): add_library cannot create ALIAS target "KF5::SysGuard" because target "KSysGuard::SysGuard" is IMPORTED. Call Stack (most recent call first): /home/myuser/kde/usr/lib/x86_64-linux-gnu/cmake/KF5SysGuard/KF5SysGuardConfig.cmake:37 (add_sysguard_target) /home/myuser/kde/usr/share/ECM/find-modules/FindKF5.cmake:74 (find_package) CMakeLists.txt:84 (find_package) My assessment is that cmake need a newer version for the current code: cmake version 3.10.2 I can't provide a minimum version number to do the job, apparently 3.17.2 does the job. SOFTWARE/OS VERSIONS Operating System: KDE neon Unstable Edition KDE Plasma Version: 5.18.80 KDE Frameworks Version: 5.71.0 Qt Version: 5.14.2 Kernel Version: 5.3.0-51-generic OS Type: 64-bit Processors: 4 × Intel® Core™ i7 CPU 920 @ 2.67GHz Memory: 7,8 GiB of RAM Graphics Processor: llvmpipe ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 419000] Canvas input navigation shortcuts not working when going to full screen mode
https://bugs.kde.org/show_bug.cgi?id=419000 vanyossi changed: What|Removed |Added Assignee|krita-bugs-n...@kde.org |ghe...@gmail.com Status|REPORTED|CONFIRMED Ever confirmed|0 |1 --- Comment #8 from vanyossi --- I can reproduce it now. It only happens sometimes going either from window to fullscreen or from fullscreen to window. Focus is "lost" during the operation an when autoregained the eventfilter is off. (or so it seems) This only happens when the input device is a mouse. Stylus is not affected. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421387] Camera Leica V-Lux (Typ 114) not supported
https://bugs.kde.org/show_bug.cgi?id=421387 Maik Qualmann changed: What|Removed |Added CC||metzping...@gmail.com --- Comment #1 from Maik Qualmann --- Leica V-Lux (Type 114) or Leica V-Lux (Type 115)? The type 114 is supported in libraw 0.20.0. Your digiKam version 5.6.0 is completely out of date (3 year old). Please test it with the digiKam-6.4.0 or the digiKam-7.0.0-RC AppImage from www.digikam.org. Maik -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420575] kdenlive-20.04.0.exe blocked by Trend Micro Maximum Security as a ransomware
https://bugs.kde.org/show_bug.cgi?id=420575 --- Comment #3 from carlo@gmail.com --- Hello, I've submitted this problem to Trend Micro and after some days (due to a TM upgrade I suppose) the problem disappeared and I was able to run the installation without the need to add the installer to the TM AV exclusion list. Best Regards Carlo -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414735] Author Data not Saved when Saving/Exporting to PNG/JPG
https://bugs.kde.org/show_bug.cgi?id=414735 --- Comment #4 from vanyossi --- Relevant related: bug 396672 bug 413970 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 414735] Author Data not Saved when Saving/Exporting to PNG/JPG
https://bugs.kde.org/show_bug.cgi?id=414735 vanyossi changed: What|Removed |Added Resolution|--- |NOT A BUG CC||ghe...@gmail.com Status|REPORTED|RESOLVED --- Comment #3 from vanyossi --- Lets close this bug. The metadata is indeed saved into the PNG and the JPG. you can check this using "imagemagick identify". The issue is that we are not reading the metadata into the document information but as Wolthera said, we put it into the layer->metadata keys. Note that we do not load all the keys into the layer metadata. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421387] New: Camera Leica V-Lux (Typ 114) not supported
https://bugs.kde.org/show_bug.cgi?id=421387 Bug ID: 421387 Summary: Camera Leica V-Lux (Typ 114) not supported Product: digikam Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Setup-Cameras Assignee: digikam-bugs-n...@kde.org Reporter: mathias.me...@icloud.com Target Milestone: --- Good day, I am running digikam 5.6 (highest version on ubuntu 18.04. Despite of being listed under "help" "supported cameras" my Leica V-Lux (Typ 115) is not listed in the configuration panel for adding cameras for import. Installed version of libraw is 0.18.8-1 (also highest available version). Digikam can display camera raw file (.rwl) but cannot edit or convert to dng. Will there be a fix in near future? Thank you very much in advance Mathias Menge -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 420635] Apps that autostart do not appear in the system tray, including DiscoverNotifier
https://bugs.kde.org/show_bug.cgi?id=420635 --- Comment #30 from Brian Wright --- AHA :-) It appears that I found the culprit - NoMachine! Based on your feedback from my last test results, I started to suspect if NoMachine was causing it. So, I did an apt-get purge --autoremove NoMachine, rebooted, and BINGO!!! Everything worked as it should - the autostarted icons appeared, and the app windows opened. The Kmix and DiscoverNotify icons were also present. Here are the latest test results. Output from journalctl -b 0 | grep StatusNotifierHost: May 11 20:54:03 bdw-desktop kded5[26589]: Registering "org.kde.StatusNotifierHost-27787" as system tray Output from listIcons.sh: org.kde.StatusNotifierWatcher pid,start,command: 26589 20:52:23 kded5 ITEMS: ITEM: :1.38/org/ayatana/NotificationItem/pasystray PID STAT: 350 20:52:32 /usr/bin/pasystray ID:pasystray TITLE: pasystray ITEM: :1.40/StatusNotifierItem PID STAT: 32563 20:52:32 /usr/bin/korgac ID:KOrganizer Reminder Daemon TITLE: KOrganizer Reminder Daemon ITEM: :1.30/StatusNotifierItem PID STAT: 30242 20:52:31 /usr/lib/x86_64-linux-gnu/libexec/DiscoverNotifier ID:Discover Notifier_org.kde.DiscoverNotifier TITLE: Updates ITEM: :1.53/StatusNotifierItem PID STAT: 1728 20:52:35 /usr/bin/kmix --keepvisibility ID:KMix TITLE: Volume Control ITEM: :1.60/StatusNotifierItem PID STAT: 31040 20:52:31 /usr/bin/keepassxc ID:KeePassXC TITLE: KeePassXC ITEM: :1.68/StatusNotifierItem PID STAT: 27858 20:52:30 /usr/bin/xembedsniproxy ID:hp-systray TITLE: hp-systray ITEM: :1.55/org/ayatana/NotificationItem/Skype1 PID STAT: 1764 20:52:35 /usr/share/skypeforlinux/skypeforlinux --executed-from=/home/bdw --pid=1714 ID:Skype1 TITLE: skypeforlinux ITEM: :1.63/org/ayatana/NotificationItem/Slack1 PID STAT: 1695 20:52:33 /usr/lib/slack/slack ID:Slack1 TITLE: slack ITEM: :1.74/StatusNotifierItem PID STAT: 9345 20:53:05 /usr/bin/kalarm --tray ID:KAlarm TITLE: KAlarm ITEM: :1.107/org/ayatana/NotificationItem/dropbox_client_1903 PID STAT: 1903 20:52:50 /home/bdw/.dropbox-dist/dropbox-lnx.x86_64-96.4.172/dropbox ID:dropbox-client-1903 TITLE: dropbox I use NoMachine to access a remote Windows box at my workplace. NoMachine appears to wreak havoc with KDE Plasma when you log in via SDDM. To be fair to NoMachine, I may have configured it incorrectly. The NoMachine server was always running in the background, and only by removing it and rebooting the machine, everything was AOK. I suggest installing NoMachine on your system (local or virtual) and set it to run the server at startup, then reboot. You should see the same thing I experienced. It seems that the NoMachine server and client are intertwined, so more testing will have to be done with the NoMachine server not running on startup. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420575] kdenlive-20.04.0.exe blocked by Trend Micro Maximum Security as a ransomware
https://bugs.kde.org/show_bug.cgi?id=420575 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420483] crashes on attempt to open
https://bugs.kde.org/show_bug.cgi?id=420483 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419958] Cannot Render Video on KdenLive 19.12.3(Installed Via Snap)
https://bugs.kde.org/show_bug.cgi?id=419958 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.
[kdenlive] [Bug 419567] Video playback is terrible!!!
https://bugs.kde.org/show_bug.cgi?id=419567 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 420680] Just have trouble using. the brush tools. The sensitivity is really slow for me.
https://bugs.kde.org/show_bug.cgi?id=420680 --- Comment #3 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 420668] Krita crashes randomly when increasing the brush size to near maximum, or trying to save a file
https://bugs.kde.org/show_bug.cgi?id=420668 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 420652] discover wont launch
https://bugs.kde.org/show_bug.cgi?id=420652 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 419899] I can't move my proyect to a second monitor
https://bugs.kde.org/show_bug.cgi?id=419899 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.
[kdenlive] [Bug 419810] Opening up the software give a broken UI with all seemingly working features except none of the features are visible
https://bugs.kde.org/show_bug.cgi?id=419810 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.
[krita] [Bug 419972] I can't export my files. I get a data error
https://bugs.kde.org/show_bug.cgi?id=419972 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 420226] Random crashes on Mac while deselecting a selection
https://bugs.kde.org/show_bug.cgi?id=420226 --- 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.
[kdenlive] [Bug 420537] properties for effects is not seeing
https://bugs.kde.org/show_bug.cgi?id=420537 --- Comment #2 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 420336] Cannot add specific number, only arrows work
https://bugs.kde.org/show_bug.cgi?id=420336 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 409749] Stylus eraser keeps resetting to basic brush
https://bugs.kde.org/show_bug.cgi?id=409749 --- Comment #4 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421356] Plasmashell crashed when on moving icon on desktop.
https://bugs.kde.org/show_bug.cgi?id=421356 --- Comment #1 from asca...@q.com --- Created attachment 128382 --> https://bugs.kde.org/attachment.cgi?id=128382=edit New crash information added by DrKonqi plasmashell (5.18.5) using Qt 5.14.2 - What I was doing when the application crashed: I'd noticed that the bottom row of icons was moved up one row, so I attempted to move them back down. The first time it caused Plasma to restart, and the second it just crashed with a DrKonqi dialog. These are the first and second times it has happened. I don't know that it will, but l selected "sometimes" since it happened more than once just now. -- Backtrace (Reduced): #4 0x7f4b61a475f5 in QVector::indexOf (this=this@entry=0x55c34445d088, t=..., from=from@entry=0) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:1010 #5 0x7f4b61a3f49e in QVector::removeOne (t=..., this=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:182 #6 QQuickItemPrivate::removeItemChangeListener (this=this@entry=0x55c34445d010, listener=listener@entry=0x55c34b62d200, types=..., types@entry=...) at items/qquickitem.cpp:3955 #7 0x7f4b61b74ada in QQuickShaderEffectSource::~QQuickShaderEffectSource (this=0x55c34b62d1e0, __in_chrg=) at items/qquickshadereffectsource.cpp:213 #8 0x7f4b61b74b39 in QQuickShaderEffectSource::~QQuickShaderEffectSource (this=0x55c34b62d1e0, __in_chrg=) at items/qquickshadereffectsource.cpp:218 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421356] Plasmashell crashed when on moving icon on desktop.
https://bugs.kde.org/show_bug.cgi?id=421356 asca...@q.com changed: What|Removed |Added CC||asca...@q.com -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 404959] Icon sizes and type inconsistency
https://bugs.kde.org/show_bug.cgi?id=404959 Dawid Wróbel changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||m...@dawidwrobel.com Ever confirmed|0 |1 Assignee|kmymoney-de...@kde.org |m...@dawidwrobel.com --- Comment #1 from Dawid Wróbel --- Thanks for reporting, I am looking into this. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 421386] New: crashes when editing a panel
https://bugs.kde.org/show_bug.cgi?id=421386 Bug ID: 421386 Summary: crashes when editing a panel Product: lattedock Version: git (master) Platform: Manjaro OS: Linux Status: REPORTED Severity: major Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: andresdor...@gmail.com Target Milestone: --- Created attachment 128381 --> https://bugs.kde.org/attachment.cgi?id=128381=edit docter konki log SUMMARY latte crashes when editing a panel. also, I have a panel on the top and on the left edge of the screen and it sometimes won't show the top panel STEPS TO REPRODUCE 1. open latte 2. edit a panel 3. crash OBSERVED RESULT crash and misbehaving auto-hide left panel EXPECTED RESULT no crash and left panel hides when not in use and unhide when the mouse is brought over Operating System: Manjaro Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Kernel Version: 5.6.12-24-tkg-pds OS Type: 64-bit Processors: 16 × AMD Ryzen 7 2700X Eight-Core Processor Memory: 15.6 GiB of RAM ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 421382] Missing kmymoney icons
https://bugs.kde.org/show_bug.cgi?id=421382 Dawid Wróbel changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Dawid Wróbel --- Digging deeper into the current state of things I can see that some icons are already available in Breeze. Let me change the status of this report to NEEDSINFO and report back once I have a better idea of which particular icons are missing. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 385880] Global Menu: does not work under wayland and causes a black screen when trying to enter its setting
https://bugs.kde.org/show_bug.cgi?id=385880 --- Comment #27 from Alexander Schlarb --- (In reply to Denis Shklyaev from comment #23) > Global menu still doesn't work on stable Plasma 5.18, but works on unstable > Plasma 5.18.80 under Wayland (latest neon Unstable). Some menu items may > work incorrect, global menu may not appear when first launch of some > application (you should launch application, then collapse its window and > maximize window again). But it works. Sorry for the noise! But which repo are you referring to? I have "user/ bionic main" and "dev/stable/ bionic main" enabled on my system, but the most recent available version is 4:5.18.5+p18.04+git20200511.1626-0. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421376] Krita hiccups while painting every few seconds
https://bugs.kde.org/show_bug.cgi?id=421376 vanyossi changed: What|Removed |Added CC||ghe...@gmail.com --- Comment #1 from vanyossi --- Sounds to me like a normal computer behaviour. CPU does use RAM to mover data in and out. Less free ram, less space to work with. Does this happen in the same conditions with an image smaller, say 250x250? It might be related to texture buffering for openGL. afaik it needs physical RAM to buffer the texture data before sending it to the videocard for rendering/processing -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421322] Copy file into symbolic link folder happen error
https://bugs.kde.org/show_bug.cgi?id=421322 --- Comment #5 from 319513...@outlook.com <319513...@outlook.com> --- I found when I copy file into a symbolic link folder's subfolder could work -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421385] New: Search result not contain Chinese file
https://bugs.kde.org/show_bug.cgi?id=421385 Bug ID: 421385 Summary: Search result not contain Chinese file Product: dolphin Version: 20.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: 319513...@outlook.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 128380 --> https://bugs.kde.org/attachment.cgi?id=128380=edit Search result SUMMARY STEPS TO REPRODUCE 1. Open dolphin and press 'Ctrl + F' or 'Ctrl + Shift F' 2. Try search Chinese file 3. Don't show any result OBSERVED RESULT Could search English file, but not suit for Chinese file, I guess this problem happen with other language, such Japanese and Korean. EXPECTED RESULT Show Chinese file correctly at search result Operating System: Arch Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Kernel Version: 5.6.11-arch1-1 OS Type: 64-bit Processors: 8 × Intel® Core™ i7-8550U CPU @ 1.80GHz Memory: 15.5 GiB ADDITIONAL INFORMATION This problem happen with any folder, whether it is symbolic link or not. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 421382] Missing kmymoney icons
https://bugs.kde.org/show_bug.cgi?id=421382 --- Comment #3 from Dawid Wróbel --- Here's a list of theme mappings kmymoney currently uses for its icons: https://cgit.kde.org/kmymoney.git/tree/kmymoney/icons/icons.cpp The mapping is created using the following logic: 1) load all the common icons, as defined by getCommonNames() 2) load all KDE icons, as defined by getKDENames(). If any were defined already, replace them. 3) load selected theme icons, as defined by getBreezeNames(), getTangoNames(), getOxygenNames(). If any were defined already, replace them. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421291] Plasma crashes when I drag an icon on desktop
https://bugs.kde.org/show_bug.cgi?id=421291 user.li...@outlook.com changed: What|Removed |Added CC||user.li...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 421382] Missing kmymoney icons
https://bugs.kde.org/show_bug.cgi?id=421382 --- Comment #2 from Dawid Wróbel --- It also looks like Skrooge has already had its Breeze icons moved upstream: https://forum.kde.org/viewtopic.php?f=210=126929 https://cgit.kde.org/skrooge.git/commit/?id=161912ca12001a540a4248c96bb2fdd7c82add6b -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 421382] Missing kmymoney icons
https://bugs.kde.org/show_bug.cgi?id=421382 --- Comment #1 from Dawid Wróbel --- Note that there is a project dedicated to cataloging/managing KDE finance icons, and this effort could also serve Skrooge: https://techbase.kde.org/Projects/KdeFinanceCommonIcons -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421322] Copy file into symbolic link folder happen error
https://bugs.kde.org/show_bug.cgi?id=421322 319513...@outlook.com <319513...@outlook.com> changed: What|Removed |Added Resolution|DUPLICATE |--- Status|RESOLVED|REPORTED --- Comment #4 from 319513...@outlook.com <319513...@outlook.com> --- this bug still exist after rollback to plasma-workspace-5.18.5-2 and plasma-desktop-5.18.5-2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kwayland] [Bug 421384] New: plasma-wayland-protocols fails to install
https://bugs.kde.org/show_bug.cgi?id=421384 Bug ID: 421384 Summary: plasma-wayland-protocols fails to install Product: frameworks-kwayland Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: mgraess...@kde.org Reporter: bluescreenaven...@gmail.com CC: kwin-bugs-n...@kde.org Target Milestone: --- SUMMARY It seems it's caused by commit 625a52ec8c48f61fc65dbd03054762b3485f4d68 OBSERVED RESULT I get these errors building plasma-wayland-protocols master Install the project... -- Install configuration: "Release" -- Installing: //opt/lib/i386-linux-gnu/cmake/PlasmaWaylandProtocols/PlasmaWaylandProtocolsConfig.cmake -- Installing: //opt/lib/i386-linux-gnu/cmake/PlasmaWaylandProtocols/PlasmaWaylandProtocolsConfigVersion.cmake -- Installing: //opt/share/plasma-wayland-protocols/appmenu.xml -- Installing: //opt/share/plasma-wayland-protocols/blur.xml -- Installing: //opt/share/plasma-wayland-protocols/contrast.xml -- Installing: //opt/share/plasma-wayland-protocols/dpms.xml -- Installing: //opt/share/plasma-wayland-protocols/fake-input.xml -- Installing: //opt/share/plasma-wayland-protocols/fullscreen-shell.xml -- Installing: //opt/share/plasma-wayland-protocols/idle.xml -- Installing: //opt/share/plasma-wayland-protocols/keystate.xml -- Installing: //opt/share/plasma-wayland-protocols/outputdevice.xml -- Installing: //opt/share/plasma-wayland-protocols/output-management.xml CMake Error at src/cmake_install.cmake:41 (file): file INSTALL cannot find "/srcbuild/kf5-plasma-wayland-protocols/src/protocols/plasma-effects.xml": No such file or directory. Call Stack (most recent call first): cmake_install.cmake:49 (include) make: *** [Makefile:94: install] Error 1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 421383] New: add the ability to use phone's camera and microphone on desktop
https://bugs.kde.org/show_bug.cgi?id=421383 Bug ID: 421383 Summary: add the ability to use phone's camera and microphone on desktop Product: kdeconnect Version: unspecified Platform: Other OS: All Status: REPORTED Severity: wishlist Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: miss_bar...@outlook.com Target Milestone: --- for example taking pictures in Kamera app from phone's camera over the air using kde connect or using phone's microphone as a normal input device -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 414913] Connect Deamon closed unexpectedly in Slideshow remote menu
https://bugs.kde.org/show_bug.cgi?id=414913 m...@tinet.org changed: What|Removed |Added CC||m...@tinet.org -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 421382] New: Missing kmymoney icons
https://bugs.kde.org/show_bug.cgi?id=421382 Bug ID: 421382 Summary: Missing kmymoney icons Product: Breeze Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: m...@dawidwrobel.com CC: kain...@gmail.com Target Milestone: --- Created attachment 128379 --> https://bugs.kde.org/attachment.cgi?id=128379=edit Current Windows build icons situation SUMMARY Breeze theme misses kmymoney-specific icons. At this point, craft-generated Windows and macOS packages deliver an icontheme.rcc with embedded default Breeze theme. KMyMoney *does* package and handle its own, context-specific icons, but only for oxygen, hi-color and Tango themes: https://cgit.kde.org/kmymoney.git/tree/kmymoney/icons Some third party themes like Papirus also provide their own kmymoney icons (https://github.com/PapirusDevelopmentTeam/papirus-icon-theme/commit/bbf78721433f7b902f3d40fc13ba733e84136bd0, https://github.com/PapirusDevelopmentTeam/papirus-icon-theme/commit/68c73c9c6815c9aba3d75cb42230980641cde890) It would be great if Breeze added missing icons upstream, so that kmymoney could default to using Breeze icon-set across all of the builds and simplify the codebase. -- You are receiving this mail because: You are watching all bug changes.
[choqok] [Bug 421381] New: choqok incorrectly depends on KF5Purpose
https://bugs.kde.org/show_bug.cgi?id=421381 Bug ID: 421381 Summary: choqok incorrectly depends on KF5Purpose Product: choqok Version: Git Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: scarp...@kde.org Reporter: eugene.shalygin+bugzilla@gmail.com Target Milestone: --- SUMMARY find_package(KF5Purpose) is the last one for KF5, and when it is not found cmake considers the whole KF5 package to be not found and configuring fails. STEPS TO REPRODUCE 1. cmake -DCMAKE_DISABLE_FIND_PACKAGE_KF5Purpose=ON OBSERVED RESULT -- The following REQUIRED packages have not been found: * KF5 CMake Error at /usr/share/cmake/Modules/FeatureSummary.cmake:457 (message): feature_summary() Error: REQUIRED package(s) are missing, aborting CMake run. Call Stack (most recent call first): CMakeLists.txt:79 (feature_summary) cmake 3.17.2 -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 353722] background lost multi-monitor setup
https://bugs.kde.org/show_bug.cgi?id=353722 --- Comment #10 from Mika Norén --- Distribution: Arch Linux. KDE Frameworks 5.70.0 Qt 5.14.2 (built against 5.14.2) plasmashell 5.18.5 As previously mentioned, I also have to manually edit ~/.config/plasmashellrc, section [ScreenConnectors]. I there simply delete the mysterious :0.0 that pops up from seemingly nowhere. The number it's assigned to may is random. sometimes it's right in between the other displayport screens: 0=DisplayPort-0 1=:0.0 2=DisplayPort-1 Sometimes it appears at the end: 0=DisplayPort-0 1=DisplayPort-1 2=:0.0 Sometimes it doesn't appear at all (As it should be): 0=DisplayPort-0 1=DisplayPort-1 I manually edit the mentioned file and remove the :0.0 and rearrange the numbering order of the other displayports. Then I restart plasmashell and I get back to where it's supposed to be. After the next sleep/hibernation/reboot it might or might not get randomized again. Then I have to rinse and repeat the procedure. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 421380] New: Updates task bar link crashes discover.
https://bugs.kde.org/show_bug.cgi?id=421380 Bug ID: 421380 Summary: Updates task bar link crashes discover. Product: Discover Version: 5.12.8 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: discover Assignee: lei...@leinir.dk Reporter: waricht...@yahoo.com CC: aleix...@kde.org Target Milestone: --- Application: plasma-discover (5.12.8) Qt Version: 5.9.5 Frameworks Version: 5.44.0 Operating System: Linux 4.15.0-99-generic x86_64 Distribution: Ubuntu 18.04.4 LTS -- Information about the crash: - What I was doing when the application crashed: Clicking on task bar link to apply updates. This started happening 1-2 weeks ago. now using apt to update until resolved. The crash can be reproduced every time. -- Backtrace: Application: Discover (plasma-discover), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7efbff6a0800 (LWP 1683))] Thread 10 (Thread 0x7efba7fff700 (LWP 1699)): #0 0x7efbfac81839 in syscall () at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 0x7efbfb383775 in QBasicMutex::lockInternal() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #2 0x7efbf8bf2f96 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #3 0x7efbf8bf3835 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #4 0x7efbf8bcf8cc in QSslSocket::startClientEncryption() () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #5 0x7efbf8bd0578 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #6 0x7efbf8bd8379 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #7 0x7efbfb599555 in QMetaObject::activate(QObject*, int, int, void**) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7efbf8ba2f09 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #9 0x7efbf8ba5e78 in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #10 0x7efbf8bb67ed in () at /usr/lib/x86_64-linux-gnu/libQt5Network.so.5 #11 0x7efbfd83e83c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #12 0x7efbfd846104 in QApplication::notify(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #13 0x7efbfb56a8d8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #14 0x7efbfb5c44ed in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #15 0x7efbf546b417 in g_main_context_dispatch () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #16 0x7efbf546b650 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #17 0x7efbf546b6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #18 0x7efbfb5c38ab in QEventDispatcherGlib::processEvents(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #19 0x7efbfb56890a in QEventLoop::exec(QFlags) () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #20 0x7efbfb38723a in QThread::exec() () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #21 0x7efbfb38c17d in () at /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x7efbf759a6db in start_thread (arg=0x7efba7fff700) at pthread_create.c:463 #23 0x7efbfac8788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 9 (Thread 0x7efbb5412700 (LWP 1697)): #0 0x7efbfac760b4 in __GI___libc_read (fd=25, buf=0x7efbb5411cd0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:27 #1 0x7efbf54b02b0 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efbf546b0b7 in g_main_context_check () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efbf546b570 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efbf546b962 in g_main_loop_run () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7efbd0fe0276 in () at /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0 #6 0x7efbf5493175 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x7efbf759a6db in start_thread (arg=0x7efbb5412700) at pthread_create.c:463 #8 0x7efbfac8788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 8 (Thread 0x7efbb5c13700 (LWP 1696)): #0 0x7efbfac7abf9 in __GI___poll (fds=0x565557fbe760, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7efbf546b5c9 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7efbf546b6dc in g_main_context_iteration () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7efbf546b721 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7efbf5493175 in () at /usr/lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7efbf759a6db in start_thread (arg=0x7efbb5c13700) at pthread_create.c:463 #6 0x7efbfac8788f in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7efbc5450700 (LWP 1692)): #0 0x7efbf75a09f3 in
[plasmashell] [Bug 421379] New: Deleting or moving shortcuts/application links crashes the Plasma shell.
https://bugs.kde.org/show_bug.cgi?id=421379 Bug ID: 421379 Summary: Deleting or moving shortcuts/application links crashes the Plasma shell. Product: plasmashell Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: ninjako...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY STEPS TO REPRODUCE 1. Download Plasma 5.18.5 from Pacman 2. Place a shortcut/application link on your desktop or in a folder. 3. Delete or move the shortcut/application link. OBSERVED RESULT Shell crash, desktop turns black and shell restarts. EXPECTED RESULT The shortcut is moved/deleted. SOFTWARE/OS VERSIONS Linux (Arch): 9.3.0-1 Kernel: 5.4.39-1-lts (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION: Crash log (From Ksyslogs): https://pastebin.com/aCtHiNz4 -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 421378] Error: Could not find the program 'konsole' when application set to Launch in Terminal
https://bugs.kde.org/show_bug.cgi?id=421378 m...@rhoatech.com changed: What|Removed |Added Status|RESOLVED|VERIFIED -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 421374] "Could not find the program ‘konsole’ error" after Plasma 5.18.5 update.
https://bugs.kde.org/show_bug.cgi?id=421374 m...@rhoatech.com changed: What|Removed |Added CC||m...@rhoatech.com --- Comment #1 from m...@rhoatech.com --- *** Bug 421378 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 421378] Error: Could not find the program 'konsole' when application set to Launch in Terminal
https://bugs.kde.org/show_bug.cgi?id=421378 m...@rhoatech.com changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from m...@rhoatech.com --- Likely the same bug https://bugs.kde.org/show_bug.cgi?id=421374 *** This bug has been marked as a duplicate of bug 421374 *** -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 421378] New: Error: Could not find the program 'konsole' when application set to Launch in Terminal
https://bugs.kde.org/show_bug.cgi?id=421378 Bug ID: 421378 Summary: Error: Could not find the program 'konsole' when application set to Launch in Terminal Product: kmenuedit Version: 5.18.5 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: m...@rhoatech.com Target Milestone: --- Created attachment 128378 --> https://bugs.kde.org/attachment.cgi?id=128378=edit error-krunner SUMMARY I have a script that I created an associated application for which I would typically launch in krunner or application menu. This application is set to "Launch in Terminal". When attempting to run, from either the application menu in Latte Dock or krunner, an error is shown "Could not find the program 'konsole'". This error is not shown if the application is not set to "Launch in Terminal" STEPS TO REPRODUCE 1. Create an application to "Launch in terminal" 2. Attempt to run the application OBSERVED RESULT Error is shown "Could not find the program 'konsole'" EXPECTED RESULT Application successfully runs in terminal SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Kernel Version: 5.6.11-arch1-1 OS Type: 64-bit Processors: 12 × Intel® Core™ i7-10710U CPU @ 1.10GHz Memory: 15.5 GiB of RAM ADDITIONAL INFORMATION Error log: May 12 09:35:03 bumblebee krunner[15990]: Internal program error. QStandardPaths::findExecutable couldn't find "konsole" but our own logic found it at "/usr/bin/konsole" . Please report a bug at https://bugs.kde.org -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 421377] Inconsistant search results
https://bugs.kde.org/show_bug.cgi?id=421377 --- Comment #1 from Christoph Vogtländer --- Created attachment 128377 --> https://bugs.kde.org/attachment.cgi?id=128377=edit No item count with message in list -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 421377] New: Inconsistant search results
https://bugs.kde.org/show_bug.cgi?id=421377 Bug ID: 421377 Summary: Inconsistant search results Product: kmail2 Version: 5.14.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: kdepim-b...@kde.org Reporter: k...@mockies.de Target Milestone: --- Created attachment 128376 --> https://bugs.kde.org/attachment.cgi?id=128376=edit Serch dialogue with result and no hits SUMMARY Searching for e.g. "Important" messages will sometimes result in messages to be shown in the search dialogue, but at the bottom "0 matches" are stated (see attachment). Leaving the dialogue will show an empty search folder. The message is marked as "Important" and should be shown. Eventually (not after simply pressing F5, though), the message will be shown correctly even in the search folder. Also, the message count of the search folder is not shown correctly. Even when a message is present in the messages list, the item count in the tool tip and folder list is "". Behaviour seems to be triggered when using "Search in all folders", but also has been observed when using "Search only in" Restarting kmail seems to solve the issue STEPS TO REPRODUCE 1. create a new search 2. "Search in all folders" 3. "Message Status" is "Important" 4. Press "Search" -> Message is shown, but "0 matches", search folder is empty 5. Switch to "Search only in" and select top level entry, with sub-folders 6. Press "Search" -> Nothing changes 7. Press "Search" (why pressing twice is needed is unclear) -> "1 match" is shown OBSERVED RESULT Unexpected and inconstant search result behaviour EXPECTED RESULT With any setting, the correct results should be shown SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 Kernel Version: 5.6.11-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-4460 CPU @ 3.20GHz Memory: 15,3 GiB -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421376] New: Krita hiccups while painting every few seconds
https://bugs.kde.org/show_bug.cgi?id=421376 Bug ID: 421376 Summary: Krita hiccups while painting every few seconds Product: krita Version: 4.3.0-beta1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: tamtamy.tym...@gmail.com Target Milestone: --- SUMMARY When my PC is under a heavy load, usually when my RAM is kinda full (I guess around 80-90%?) even though CPU is free, Krita sometimes has a hiccup. This is not related to autosave since it happens way too often. It seems to be regular. Note: there is a chance it happens under lower load as well but I don't notice it as much? STEPS TO REPRODUCE 1. Open programs to take up a lot of RAM. 2. Paint one consistent line for a long time, quite quickly. (It doesn't need to be one stroke, but it helps seeing the problem). EXPECTED RESULT The line is being drawn all the time consistently. OBSERVED RESULT Sometimes the line stops, but then restarts - it is just a visual lag, since the underlying stroke has the same shape as other parts of the stroke. ADDITIONAL INFO The lag happens around every 5 seconds. Also when I tried to use a simple applet, I had a problem recording the video because I had a huge lag all the time - and the stroke shape was different, because, I believe, Krita didn't get enough tablet events because of the heavy performance needs. That suggests that in this case it might be something inside of Krita instead of my system? NOTE: It can of course still be my system... Also Krita 4.3.0 I think has the same issue, and I'm not sure if it's a regression or not. I will check further. I'd like to leave it here so other people (1) can see the video and check if it looks familiar, (2) can tell me it's all because my system is bad and doesn't deserve a cookie, or (3)... maybe someone would guess the reason. I will check other versions to see which has it. Recorded screen video: https://drive.google.com/open?id=1KRegM9sjgjqhWadxpBTz7OK59Y6XbNef SOFTWARE/OS VERSIONS Krita git version: built upon b9b20f3376 Krita Version: 5.0.0-prealpha (git a23d232) Languages: en_US, en, en_US, en, en_US, en, pl, pl_PL, pl Hidpi: true Qt Version (compiled): 5.11.1 Version (loaded): 5.11.1 OS Information Build ABI: x86_64-little_endian-lp64 Build CPU: x86_64 CPU: x86_64 Kernel Type: linux Kernel Version: 5.3.7-050307-generic Pretty Productname: Linux Mint 19.3 Product Type: linuxmint Product Version: 19.3 Desktop: X-Cinnamon -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 421375] New: Scrollbar mini-map is always turned on
https://bugs.kde.org/show_bug.cgi?id=421375 Bug ID: 421375 Summary: Scrollbar mini-map is always turned on Product: kate Version: 20.04.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: part Assignee: kwrite-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com Target Milestone: --- SUMMARY After last update - mainly KFrameworks from 5.69 to 5.70 - in all editors based on kate (text editor) component like KWrite, KDevelop and others, "Scrollbar mini-map" became always turned on. Switching option in configuration doesn't work. Restart application doesn't work. I tested following applications: KWrite, Kate, KDevelop STEPS TO REPRODUCE 1. Start Kate, Kwrite, KDevelop 2. If you have Scrollbar mini-map turned on please turn it off 3. OBSERVED RESULT "Scrollbar mini-map" is always turned on. EXPECTED RESULT "Scrollbar mini-map" should be turned off if proper option is not checked. SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421322] Copy file into symbolic link folder happen error
https://bugs.kde.org/show_bug.cgi?id=421322 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE --- Comment #3 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 421213 *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421213] Regression: Can no longer copy/move files into a symlinked folder
https://bugs.kde.org/show_bug.cgi?id=421213 Patrick Silva changed: What|Removed |Added CC||319513...@outlook.com --- Comment #4 from Patrick Silva --- *** Bug 421322 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 420959] Error plotting
https://bugs.kde.org/show_bug.cgi?id=420959 Nikita Sirgienko changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/kde/ ||cantor/commit/87172a9416a89 ||49cc80350b733d771d7b01d90f3 Version Fixed In||20.07.70 --- Comment #20 from Nikita Sirgienko --- Git commit 87172a9416a8949cc80350b733d771d7b01d90f3 by Nikita Sirgienko. Committed on 11/05/2020 at 22:37. Pushed by sirgienko into branch 'master'. [Octave] Add check, if Octave can have write in temporary dir FIXED-IN: 20.07.70 M +2-1src/backends/octave/CMakeLists.txt M +1-1src/backends/octave/octaveexpression.cpp M +48 -2src/backends/octave/octavesession.cpp M +3-0src/backends/octave/octavesession.h M +1-1src/lib/CMakeLists.txt M +38 -0src/lib/backend.cpp M +8-1src/lib/backend.h https://invent.kde.org/kde/cantor/commit/87172a9416a8949cc80350b733d771d7b01d90f3 -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 421288] Unable to delete some categories
https://bugs.kde.org/show_bug.cgi?id=421288 --- Comment #5 from Jack --- Rather than leave the delete enabled, and then have to block it anyway, I would much prefer to see a better way to inform the use of why the delete (or, in fact any action) is not allowed. Displaying that information in a tool-tip would work, but it might also be reasonable to show it in a status are, such as at the bottom of the main window. I think this is actually a much broader issue than just not being able to delete some object. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 372402] touchpad disabled intermittently in KDE when running KMyMoney
https://bugs.kde.org/show_bug.cgi?id=372402 Jack changed: What|Removed |Added CC||ostroffjh@users.sourceforge ||.net --- Comment #1 from Jack --- The migration from KDE4 libs to KF5 Frameworks change a great deal of the underlying. Is this still a problem? I'm guessing this could be closed as UNMAINTAINED. -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 421345] Automatically close Clipboard applet after clearing history or deleting the last element
https://bugs.kde.org/show_bug.cgi?id=421345 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 421350] RMB on a monitor chart with non-focused ksysguard window is painted outside a window with window decorations.
https://bugs.kde.org/show_bug.cgi?id=421350 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #2 from Patrick Silva --- possible duplicate of bug 417378 -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 421362] find_package XCB Warning (dev) invalid package name passed to find_package_handle_standard_args does not match calling package
https://bugs.kde.org/show_bug.cgi?id=421362 --- Comment #2 from Alex --- Awesome, thanks! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 361740] Disable warning "The document requested to be launched in presentation mode" on document reload
https://bugs.kde.org/show_bug.cgi?id=361740 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 179678] KIO needs PolicyKit-kde integration
https://bugs.kde.org/show_bug.cgi?id=179678 blueb...@eyepaste.com changed: What|Removed |Added CC||blueb...@eyepaste.com --- Comment #95 from blueb...@eyepaste.com --- So, this bug is pestering KDE users for a decade already. Is David Faure still alive or does he has other hobbies nowadays? Isn't this a sign on the wall to NOT use KIO at all and revert back to the state that it just worked? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421298] Clicking http(s) links results into endless 'downloading file' dialogue instead of passing link to web browser
https://bugs.kde.org/show_bug.cgi?id=421298 --- Comment #9 from Albert Astals Cid --- Just to double check, you don't have any proxy set at kcmshell5 proxy right? -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421027] Different fonts chosen to replace Helvetica inside and outside flatpak
https://bugs.kde.org/show_bug.cgi?id=421027 --- Comment #11 from Albert Astals Cid --- According to https://github.com/flatpak/flatpak/issues/1563 it seems it's just one of those things that it's not polished enough yet in flatpak -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 371849] audio file sounds "clicky" when on project timeline; affects rendered file
https://bugs.kde.org/show_bug.cgi?id=371849 lethal.lo...@gmail.com changed: What|Removed |Added CC||lethal.lo...@gmail.com --- Comment #38 from lethal.lo...@gmail.com --- Created attachment 128375 --> https://bugs.kde.org/attachment.cgi?id=128375=edit Video of Kdenlive glitchy audio with empty timeline and a jpeg I also hear clicks and pops, or static, or crackling sounds when playing back the timeline without even adding in any audio, as can be seen in the attached video. Kdenlive 20.04.0 Windows 10 64-bit 1909 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 421329] New Global Shortcuts KCM: shortcut to launch an app doesn't work
https://bugs.kde.org/show_bug.cgi?id=421329 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=417495 -- You are receiving this mail because: You are watching all bug changes.
[khotkeys] [Bug 417495] Application launcher shortcuts well recorded but launch nothing
https://bugs.kde.org/show_bug.cgi?id=417495 Christoph Feck changed: What|Removed |Added See Also||https://bugs.kde.org/show_b ||ug.cgi?id=421329 -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 421374] New: "Could not find the program ‘konsole’ error" after Plasma 5.18.5 update.
https://bugs.kde.org/show_bug.cgi?id=421374 Bug ID: 421374 Summary: "Could not find the program ‘konsole’ error" after Plasma 5.18.5 update. Product: kmenuedit Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: lnx...@westlot.net Target Milestone: --- SUMMARY After the 5.18.5 update, I get a "Could not find the program ‘konsole’ error" when trying to launch executable scripts directly with 'Run in terminal' checked in Advanced tab in the Menu Editor. STEPS TO REPRODUCE 1. Have executable script (python, bash, etc) in Application Menu set to run in terminal with command "[path to script]/hello.sh" 2. Open Application Menu and select script to run. OBSERVED RESULT Error dialog stating "Could not find the program ‘konsole’" is displayed. EXPECTED RESULT Konsole opens with running script. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.18 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 ADDITIONAL INFORMATION Konsole itself runs fine from the Application Menu and a terminal window. This appears to only affect applications set to run in a terminal from within the Application Menu. This is also reported on the Manjaro forums: https://forum.manjaro.org/t/could-not-find-the-program-konsole-error-after-manjaro-update/140484 I realise this is probably not a kmenuedit bug, but there is no Application Menu section and I have no idea where this should go. -- You are receiving this mail because: You are watching all bug changes.
[ksudoku] [Bug 421332] I'm using SolydX linux. Have used KSudoku a long time. Now, after updating SolydX, KSudoku will not store the game.
https://bugs.kde.org/show_bug.cgi?id=421332 Albert Astals Cid changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO CC||aa...@kde.org --- Comment #1 from Albert Astals Cid --- Maybe you can tell us the version you are using now? (and ideally the one you were using before). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421322] Copy file into symbolic link folder happen error
https://bugs.kde.org/show_bug.cgi?id=421322 --- Comment #2 from Dzen Pythom --- Created attachment 128374 --> https://bugs.kde.org/attachment.cgi?id=128374=edit krusader bug -- You are receiving this mail because: You are watching all bug changes.
[neon] [Bug 421358] libKDevPlatformTests.so.55 missing in kdevplatform55-libs package
https://bugs.kde.org/show_bug.cgi?id=421358 Kevin Funk changed: What|Removed |Added CC||ralf.habac...@freenet.de --- Comment #2 from Kevin Funk --- This a side effect of bug 409951. See https://bugs.kde.org/show_bug.cgi?id=409951#c4 and following comments for more details. Would need some redesign of kdevplatform library code, ideally. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421322] Copy file into symbolic link folder happen error
https://bugs.kde.org/show_bug.cgi?id=421322 Dzen Pythom changed: What|Removed |Added CC||zgwe...@gmail.com --- Comment #1 from Dzen Pythom --- Confirm bug on krusader app. This bug was active when I update two packages - plasma-desktop and plasma-workspace. Rollig out this update fixes bug. python@pekarnya OS: Arch Linux x86_64 Host: HP ProDesk 600 G1 SFF Kernel: 5.6.11-arch1-1 Uptime: 4 hours, 46 mins Shell: fish 3.1.2 DE: Plasma 5.18.5-2 KDE Frameworks Version: 5.70.0 Qt Version: 5.14.2 CPU: Intel i3-4130 (4) @ 3.400GHz GPU: Intel 4th Generation Core Processor Family Memory: 9687MiB -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 421373] New: Emojis aren't rendered to the grid in the emoji picker, making it rather hard to pick them.
https://bugs.kde.org/show_bug.cgi?id=421373 Bug ID: 421373 Summary: Emojis aren't rendered to the grid in the emoji picker, making it rather hard to pick them. Product: plasmashell Version: 5.18.4 Platform: Kubuntu Packages OS: Linux Status: REPORTED Severity: major Priority: NOR Component: Emoji picker Assignee: plasma-b...@kde.org Reporter: robertsdavid...@gmail.com Target Milestone: 1.0 Created attachment 128373 --> https://bugs.kde.org/attachment.cgi?id=128373=edit A screenshot of the emoji picker, scrolled down a bit, displaying some emojis off-grid and the selector and tofu on-grid. SUMMARY Emojis aren't rendered to the grid in the emoji picker, making it rather hard to pick them. STEPS TO REPRODUCE 1. Start emoji picker. OBSERVED RESULT Emojis are offset from the grid table they're in. Selector and tofu is not. EXPECTED RESULT Emojis are rendered to the same grid as everything else. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 20.04 LTS KDE Plasma Version: 5.18.4 KDE Frameworks Version: 5.68.0 Qt Version: 5.12.8 ADDITIONAL INFORMATION Perhaps my use of noto-color-emoji has something to do with this? Or the screen scaling factor of 1.6? I'm assuming Emoji Picker version is the same as KDE version, since I can't find a package or figure out how to bring up an about menu in the Emoji Picker. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421372] New: Search Buttons Move to Right
https://bugs.kde.org/show_bug.cgi?id=421372 Bug ID: 421372 Summary: Search Buttons Move to Right Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: anditosan1...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- SUMMARY In the search for dolphin files, the close tab button appears on the left instead of the predictable right. I would like to request visual consistency in the ui by moving the close button to the right on the search tabs, like the rest of the ui. 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.
[plasma-nm] [Bug 421371] New: UX: Disable WIFI and Airplane Mode Need Explanation
https://bugs.kde.org/show_bug.cgi?id=421371 Bug ID: 421371 Summary: UX: Disable WIFI and Airplane Mode Need Explanation Product: plasma-nm Version: 5.18.5 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: anditosan1...@gmail.com Target Milestone: --- SUMMARY Currently, the nm applet shows wifi networks only. The applet is able to turn on airplane mode that additionally stops Bluetooth connectivity. This distinction is not clear from the UI. The UI would probably need, * Popup messages shown on hover indicating what each checkbox does. (i.e. WIFI disable wifi, airplane mode, "disable wifi and bluetooth) 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.
[extra-cmake-modules] [Bug 421362] find_package XCB Warning (dev) invalid package name passed to find_package_handle_standard_args does not match calling package
https://bugs.kde.org/show_bug.cgi?id=421362 Christophe Giboudeaux changed: What|Removed |Added Latest Commit|8d181637a0334eff48bebd8b6e2 |https://cgit.kde.org/extra- |1db3884f3c180 |cmake-modules.git/commit/?i ||d=8d181637a0334eff48bebd8b6 ||e21db3884f3c180 -- You are receiving this mail because: You are watching all bug changes.
[extra-cmake-modules] [Bug 421362] find_package XCB Warning (dev) invalid package name passed to find_package_handle_standard_args does not match calling package
https://bugs.kde.org/show_bug.cgi?id=421362 Christophe Giboudeaux changed: What|Removed |Added Version Fixed In||5.71.0 Resolution|--- |FIXED Latest Commit||8d181637a0334eff48bebd8b6e2 ||1db3884f3c180 Status|REPORTED|RESOLVED --- Comment #1 from Christophe Giboudeaux --- Already fixed https://phabricator.kde.org/D29396 -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 421342] Files lost after being told they cannot be saved
https://bugs.kde.org/show_bug.cgi?id=421342 David Hurka changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #3 from David Hurka --- We don’t need to evaluate how Okular should behave when files are deleted, we already did that in the other bug. I don’t know how to fix this; the fix is already in production code, but I don’t know why it doesn’t work. Maybe it is just that people compile Okular without OKULAR_KEEP_FILE_OPEN? *** This bug has been marked as a duplicate of bug 402017 *** -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 402017] Cannot save PDF when loaded file has been deleted
https://bugs.kde.org/show_bug.cgi?id=402017 David Hurka changed: What|Removed |Added CC||markjball...@googlemail.com --- Comment #10 from David Hurka --- *** Bug 421342 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 421363] Transform to tiny size causes Krita to crash to desktop
https://bugs.kde.org/show_bug.cgi?id=421363 David REVOY changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||i...@davidrevoy.com Ever confirmed|0 |1 --- Comment #1 from David REVOY --- Good one! I can reproduce this one easily on 4.3beta appimage on Kubuntu Linux. I'm switching it to confirmed. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 358418] Allow widgets to optionally not snap to a grid
https://bugs.kde.org/show_bug.cgi?id=358418 --- Comment #25 from Pep --- I don't know how to delete my previous post so i want to state that i regret i have written it. It is not the mood we need, to talk about anything, and i am sorry i didn't respected the code of conduct. But i wasn't just making a rant, the problem exist and there are workarounds. There are two points i think deserve to be saved in my previous post: 1 - install all KDE but NOT Plasma. I use XFCE as a lightweight, highly configurable desktop and use all the KDE package in it. 2 - write obscure magical formulas in a very well buried configuration file. as recommended here https://forum.kde.org/viewtopic.php?f=289=156646 And maybe in 4 years more i can learn how to write a script i can run: just put a number as a parameter and run it... meanwhile, excuse me -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421361] Removing a keyboard shortcut crashes Digikam
https://bugs.kde.org/show_bug.cgi?id=421361 Maik Qualmann changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED CC||metzping...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421361] Removing a keyboard shortcut crashes Digikam
https://bugs.kde.org/show_bug.cgi?id=421361 Maik Qualmann changed: What|Removed |Added Version Fixed In||7.0.0 Latest Commit||https://invent.kde.org/kde/ ||digikam/commit/4d66ad00c8cd ||9d888b6b05eb241c9da35da64c7 ||6 --- Comment #2 from Maik Qualmann --- Git commit 4d66ad00c8cd9d888b6b05eb241c9da35da64c76 by Maik Qualmann. Committed on 11/05/2020 at 20:38. Pushed by mqualmann into branch 'master'. do not delete QAction via sender from the dialog The QAction will later be deleted in the dialog. FIXED-IN: 7.0.0 M +2-1NEWS M +9-6core/libs/tags/engine/tagsactionmngr.cpp M +2-2core/libs/tags/engine/tagsactionmngr.h https://invent.kde.org/kde/digikam/commit/4d66ad00c8cd9d888b6b05eb241c9da35da64c76 -- You are receiving this mail because: You are watching all bug changes.
[plasma-nm] [Bug 421370] New: Indicate Network Search Happening
https://bugs.kde.org/show_bug.cgi?id=421370 Bug ID: 421370 Summary: Indicate Network Search Happening Product: plasma-nm Version: 5.18.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: anditosan1...@gmail.com Target Milestone: --- SUMMARY Plasma nm applet needs to indicate that it is searching for nearby networks. Currently, the process clears the list of networks and after a few seconds it populates again. This "could" be difficult for users to understand. To aid in that, include a spinner that can indicate the system is working to find additional networks. 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.
[plasma-nm] [Bug 421369] New: Unnecessary notification Appears when Disconnecting Wifi Network
https://bugs.kde.org/show_bug.cgi?id=421369 Bug ID: 421369 Summary: Unnecessary notification Appears when Disconnecting Wifi Network Product: plasma-nm Version: 5.18.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: anditosan1...@gmail.com Target Milestone: --- SUMMARY A notification appears when disconnecting from a wifi network intentionally. Since the user is already interacting and intentionally disconnecting, there should "not" be a an additional notification popup above plasma nm to indicate that the network has been disconnected. 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.
[plasma-nm] [Bug 421368] New: Diconnect Button Clears Network List
https://bugs.kde.org/show_bug.cgi?id=421368 Bug ID: 421368 Summary: Diconnect Button Clears Network List Product: plasma-nm Version: 5.18.5 Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: jgrul...@redhat.com Reporter: anditosan1...@gmail.com Target Milestone: --- SUMMARY Wifi networks list disappears when disconnecting wifi network using the network manager. The expected behavior should be that no list clear should happen as the disconnection button is clicked. 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.
[krunner] [Bug 421367] New: Crash when changing display
https://bugs.kde.org/show_bug.cgi?id=421367
Bug ID: 421367
Summary: Crash when changing display
Product: krunner
Version: 5.16.5
Platform: Ubuntu Packages
OS: Linux
Status: REPORTED
Keywords: drkonqi
Severity: crash
Priority: NOR
Component: general
Assignee: k...@privat.broulik.de
Reporter: jm-ej...@badcold.net
Target Milestone: ---
Application: krunner (5.16.5)
Qt Version: 5.12.4
Frameworks Version: 5.62.0
Operating System: Linux 5.3.0-51-generic x86_64
Distribution: Ubuntu 19.10
-- Information about the crash:
I have 2 monitors + 1 tv, one monitor has audio, the tv is not plugged directly
but passes through an amplifier
- What I was doing when the application crashed:
xrandr to go from 1 monitor + tv, to 2 mointors
pacmd to switch audio output from tv to monitor
- Unusual behavior I noticed:
When I switch the other way around, my "task manager" bar which isn't on the
primary screen disapear.
When I enable the 3 video outputs or just the tv, the screen flickers heavily
unless I force the performance level ("echo high >
/sys/class/drm/card0/device/power_dpm_force_performance_level")
The crash can be reproduced sometimes.
-- Backtrace:
Application: krunner (krunner), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f324a3b4840 (LWP 2456))]
Thread 34 (Thread 0x7f31a6ffd700 (LWP 12541)):
#0 0x7f324d6352c6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x556f9e5de490) at
../sysdeps/unix/sysv/linux/futex-internal.h:80
#1 0x7f324d6352c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x556f9e5de440, cond=0x556f9e5de468) at pthread_cond_wait.c:508
#2 0x7f324d6352c6 in __pthread_cond_wait (cond=0x556f9e5de468,
mutex=0x556f9e5de440) at pthread_cond_wait.c:638
#3 0x7f324e318dbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x7f324e318eb1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x7f320df04ea0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6 0x7f320df08c3e in () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7 0x7f320df04072 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8 0x7f320df08c99 in () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9 0x7f320df04072 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f320df08c99 in () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#11 0x7f320df04072 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#12 0x7f320df06b83 in ThreadWeaver::Thread::run() () at
/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#13 0x7f324e312c92 in () at /lib/x86_64-linux-gnu/libQt5Core.so.5
#14 0x7f324d62e669 in start_thread (arg=) at
pthread_create.c:479
#15 0x7f324df95323 in clone () at
../sysdeps/unix/sysv/linux/x86_64/clone.S:95
Thread 33 (Thread 0x7f31a77fe700 (LWP 12540)):
#0 0x7f324d6352c6 in futex_wait_cancelable (private=,
expected=0, futex_word=0x556f9e5de490) at
../sysdeps/unix/sysv/linux/futex-internal.h:80
#1 0x7f324d6352c6 in __pthread_cond_wait_common (abstime=0x0, clockid=0,
mutex=0x556f9e5de440, cond=0x556f9e5de468) at pthread_cond_wait.c:508
#2 0x7f324d6352c6 in __pthread_cond_wait (cond=0x556f9e5de468,
mutex=0x556f9e5de440) at pthread_cond_wait.c:638
#3 0x7f324e318dbf in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#4 0x7f324e318eb1 in QWaitCondition::wait(QMutex*, unsigned long) () at
/lib/x86_64-linux-gnu/libQt5Core.so.5
#5 0x7f320df04ea0 in
ThreadWeaver::Weaver::takeFirstAvailableJobOrSuspendOrWait(ThreadWeaver::Thread*,
bool, bool, bool) () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#6 0x7f320df08c3e in () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#7 0x7f320df04072 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#8 0x7f320df08c99 in () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#9 0x7f320df04072 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#10 0x7f320df08c99 in () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#11 0x7f320df04072 in
ThreadWeaver::Weaver::applyForWork(ThreadWeaver::Thread*, bool) () at
/lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#12 0x7f320df08c99 in () at /lib/x86_64-linux-gnu/libKF5ThreadWeaver.so.5
#13 0x7f320df04072 in
[cantor] [Bug 420708] Crash using ezsurf
https://bugs.kde.org/show_bug.cgi?id=420708 Nikita Sirgienko changed: What|Removed |Added Version Fixed In||20.07.70 Latest Commit||063ba6ef25f008c012782d58a14 ||b727957ac4f84 Status|ASSIGNED|RESOLVED Resolution|--- |FIXED --- Comment #11 from Nikita Sirgienko --- After 20.08 version appears possibility to change used format of plot files So, for solving your problem, you just should change the value (in Octave settings) from 'eps' to 'png' and I think, the problem will be gone. Reopen this bug, if it is not true. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 421366] New: Shortcut keys only work in English layout
https://bugs.kde.org/show_bug.cgi?id=421366 Bug ID: 421366 Summary: Shortcut keys only work in English layout Product: kdenlive Version: 20.04.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: inflo...@netc.it Target Milestone: --- SUMMARY On the Russian keyboard shortcuts do not work. This greatly slows down the workflow when placing markers to which meaningful names should be given. You have to switch to the English layout to make a marker, then to Russian to enter a name, then again to English. SOFTWARE/OS VERSIONS Ubuntu Studio 19.10 x64 Kdenlive from appimage 20.04.0b KDE Frameworks 5.68.0 Qt 5.14.1 (built against 5.14.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 421365] New: "Locate Clip" only opens a directory with a clip but does not select it
https://bugs.kde.org/show_bug.cgi?id=421365 Bug ID: 421365 Summary: "Locate Clip" only opens a directory with a clip but does not select it Product: kdenlive Version: 20.04.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: User Interface Assignee: j...@kdenlive.org Reporter: inflo...@netc.it Target Milestone: --- SUMMARY If in ProjectBin to click the "Locate clip" button, the directory with the clip will be simply opened but the clip itself will not be selected, you will have to look for it. This is very inconvenient when you delete unnecessary clips. STEPS TO REPRODUCE 1. Right Click on clip in project bin 2. Locate Clip OBSERVED RESULT A directory with a clip opens but the clip does not stand out EXPECTED RESULT The directory with the clip opens and the clip itself is highlighted SOFTWARE/OS VERSIONS Ubuntu Studio 19.10 x64 FileManager - Caja 1.22.2 Kdenlive from appimage 20.04.0b KDE Frameworks 5.68.0 Qt 5.14.1 (built against 5.14.1) The xcb windowing system -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 421364] App launched via a desktop icon opens its own desktop file
https://bugs.kde.org/show_bug.cgi?id=421364 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 421361] Removing a keyboard shortcut crashes Digikam
https://bugs.kde.org/show_bug.cgi?id=421361 caulier.gil...@gmail.com changed: What|Removed |Added CC||caulier.gil...@gmail.com --- Comment #1 from caulier.gil...@gmail.com --- Start the AppImage from a console using the "debug" argument. This will rune digiKam in GDB where you can capture a backtrace of the crash. Note : if you use the appimage file with "-debug" in file name, the backtrace will be better as this bundle include all debug symbols. Gilles Caulier -- You are receiving this mail because: You are watching all bug changes.
