[digikam] [Bug 427662] HiDPI Settings Not Working in Digikam 7.1.0
https://bugs.kde.org/show_bug.cgi?id=427662 Maik Qualmann changed: What|Removed |Added Status|REPORTED|RESOLVED Version Fixed In||7.2.0 Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 427703] kmail drag-n-drop
https://bugs.kde.org/show_bug.cgi?id=427703 Laurent Montel changed: What|Removed |Added CC||mon...@kde.org --- Comment #1 from Laurent Montel --- I think it was before akonadi support no ? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 427697] KMail did not apply data from mailto information.
https://bugs.kde.org/show_bug.cgi?id=427697 Laurent Montel changed: What|Removed |Added Latest Commit|https://invent.kde.org/pim/ |https://invent.kde.org/pim/ |messagelib/commit/6e5baafc2 |kmail/commit/a4715e7efc0909 |7748d870ab37f2fcbbfb63e53cc |c6e37dbbcf21c4309c769a1fd9 |121c| --- Comment #4 from Laurent Montel --- Git commit a4715e7efc0909c6e37dbbcf21c4309c769a1fd9 by Laurent Montel. Committed on 15/10/2020 at 05:33. Pushed by mlaurent into branch 'release/20.08'. Fix Bug 427697 - KMail did not apply data from mailto information. Add missing in-reply-to support FIXED-IN: 5.15.3 M +5-1src/job/opencomposerjob.cpp https://invent.kde.org/pim/kmail/commit/a4715e7efc0909c6e37dbbcf21c4309c769a1fd9 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 380501] Dead keys are ignored in text field
https://bugs.kde.org/show_bug.cgi?id=380501 --- Comment #7 from Feufochmar --- Updated to Plasma 5.20.0 this morning, and I don't have a problem with my password (which still contains an accented character for which I use a dead key to input it), though since the button to show the password have disappeared for me with this update, I can only confirm for one dead key, I cannot confirm for other dead keys. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 427697] KMail did not apply data from mailto information.
https://bugs.kde.org/show_bug.cgi?id=427697 Laurent Montel changed: What|Removed |Added Resolution|--- |FIXED Version Fixed In||5.15.3 Latest Commit||https://invent.kde.org/pim/ ||messagelib/commit/6e5baafc2 ||7748d870ab37f2fcbbfb63e53cc ||121c Status|REPORTED|RESOLVED --- Comment #3 from Laurent Montel --- Git commit 6e5baafc27748d870ab37f2fcbbfb63e53cc121c by Laurent Montel. Committed on 15/10/2020 at 05:21. Pushed by mlaurent into branch 'release/20.08'. Fix Bug 427697 - KMail did not apply data from mailto information. FIXED-IN: 5.15.3 M +15 -0messagecore/autotests/stringutiltest.cpp M +3-1messagecore/src/utils/stringutil.cpp https://invent.kde.org/pim/messagelib/commit/6e5baafc27748d870ab37f2fcbbfb63e53cc121c -- You are receiving this mail because: You are watching all bug changes.
[ksysguard] [Bug 427603] monitoring my NVIDIA does not show any info except temperature
https://bugs.kde.org/show_bug.cgi?id=427603 --- Comment #9 from Mathias Homann --- I just got the next nvidia driver through openSUSE updates, now I have 450.80.02. Same problem. Actually it appears to me as if nvidia-smi-[dp]mon is broken, nvidia-smi without any further parameters shows the memory consumption just fine: lemmy@kumiko:~> nvidia-smi Thu Oct 15 07:19:02 2020 +-+ | NVIDIA-SMI 450.80.02Driver Version: 450.80.02CUDA Version: 11.0 | |---+--+--+ | GPU NamePersistence-M| Bus-IdDisp.A | Volatile Uncorr. ECC | | Fan Temp Perf Pwr:Usage/Cap| Memory-Usage | GPU-Util Compute M. | | | | MIG M. | |===+==+==| | 0 GeForce GTX 1050Off | :01:00.0 On | N/A | | 35% 42CP0N/A / 75W |389MiB / 1997MiB | 0% Default | | | | N/A | +---+--+--+ -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420326] Window Titlbar not scaling correctly on Wayland
https://bugs.kde.org/show_bug.cgi?id=420326 smit changed: What|Removed |Added Summary|Window Titlbar not scalling |Window Titlbar not scaling |correctly on Wayland|correctly on Wayland -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 426574] Whenever any brushes are used, it doesn't show up
https://bugs.kde.org/show_bug.cgi?id=426574 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.
[kdevelop] [Bug 427147] Often the background parser causes crashes
https://bugs.kde.org/show_bug.cgi?id=427147 --- 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.
[kde] [Bug 176360] Cannot reposition kdesktop_lock unlocking widget
https://bugs.kde.org/show_bug.cgi?id=176360 --- 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.
[kde] [Bug 106240] MX700 Logitech Mouse Navigation
https://bugs.kde.org/show_bug.cgi?id=106240 --- 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.
[kmail2] [Bug 421726] kmail crashes opening message with QR code attached
https://bugs.kde.org/show_bug.cgi?id=421726 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kup] [Bug 422284] Recent distributions don't ship Bup anymore
https://bugs.kde.org/show_bug.cgi?id=422284 Anubhav Choudhary changed: What|Removed |Added CC||ac.10...@gmail.com --- Comment #2 from Anubhav Choudhary --- Is there any update on the issue? I too am facing the same issue for quite a time. Is there a workaround or something? -- You are receiving this mail because: You are watching all bug changes.
[calligrawords] [Bug 427736] New: Calligra Words crashed upon exit
https://bugs.kde.org/show_bug.cgi?id=427736 Bug ID: 427736 Summary: Calligra Words crashed upon exit Product: calligrawords Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: calligra-words-bugs-n...@kde.org Reporter: dougjsha...@gmail.com Target Milestone: --- Application: calligrawords (3.2.89) Qt Version: 5.15.0 Frameworks Version: 5.76.0 Operating System: Linux 5.4.0-48-generic x86_64 Windowing system: Wayland Distribution: KDE neon Unstable Edition -- Information about the crash: - What I was doing when the application crashed: I opened Calligra Words. I opened a new document. I exited without making any changes. A crash notification came up. The crash can be reproduced every time. -- Backtrace: Application: Calligra Words (calligrawords), signal: Aborted [New LWP 45657] [New LWP 45658] [New LWP 45659] [New LWP 45660] [New LWP 45661] [New LWP 45662] [New LWP 45663] [New LWP 45664] [New LWP 45665] [New LWP 45666] [New LWP 45667] [New LWP 45668] [New LWP 45669] [New LWP 45670] [New LWP 45671] [New LWP 45672] [New LWP 45673] [New LWP 45674] [New LWP 45675] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f255389daff in __GI___poll (fds=0x7ffe6005e528, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f254d849840 (LWP 45655))] Thread 20 (Thread 0x7f250a7fc700 (LWP 45675)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x557537f2aeb8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x557537f2ae68, cond=0x557537f2ae90) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x557537f2ae90, mutex=0x557537f2ae68) at pthread_cond_wait.c:638 #3 0x7f2548d3b62b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f2548d3b23b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f2550eaf609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f25538aa293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 19 (Thread 0x7f250affd700 (LWP 45674)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x557537f2aeb8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x557537f2ae68, cond=0x557537f2ae90) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x557537f2ae90, mutex=0x557537f2ae68) at pthread_cond_wait.c:638 #3 0x7f2548d3b62b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f2548d3b23b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f2550eaf609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f25538aa293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7f250b7fe700 (LWP 45673)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x557537f2aeb8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x557537f2ae68, cond=0x557537f2ae90) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x557537f2ae90, mutex=0x557537f2ae68) at pthread_cond_wait.c:638 #3 0x7f2548d3b62b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f2548d3b23b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f2550eaf609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f25538aa293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7f250bfff700 (LWP 45672)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x557537f2aeb8) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x557537f2ae68, cond=0x557537f2ae90) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x557537f2ae90, mutex=0x557537f2ae68) at pthread_cond_wait.c:638 #3 0x7f2548d3b62b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f2548d3b23b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5 0x7f2550eaf609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f25538aa293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7f2524ff9700 (LWP 45671)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x557537f2a7b0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x557537f2a760, cond=0x557537f2a788) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x557537f2a788, mutex=0x557537f2a760) at pthread_cond_wait.c:638 #3 0x7f2548d3b62b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #4 0x7f2548d3b23b in ?? () from /usr/lib/x86_64-linux-gnu/dri/radeonsi_dri.so #5
[krita] [Bug 427735] New: Animation Hotkey for new keyframe needs mouseclick on docker before it will allow triggering
https://bugs.kde.org/show_bug.cgi?id=427735 Bug ID: 427735 Summary: Animation Hotkey for new keyframe needs mouseclick on docker before it will allow triggering Product: krita Version: 4.4.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Animation Assignee: krita-bugs-n...@kde.org Reporter: mcwhi...@gmail.com Target Milestone: --- SUMMARY hotkey to make a blank frame needs reseleciton of Timeline Docker to trigger. STEPS TO REPRODUCE 1. blank frame keyframe hotkey 2. arrow key to new frame 3. *cannot hit hotkey to make new keyframe OBSERVED RESULT Need to mouseclick on the Timeline Docker to enable hotkey to trigger. 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-pa] [Bug 427734] New: Per-application output options broken in Audio Volume widget
https://bugs.kde.org/show_bug.cgi?id=427734 Bug ID: 427734 Summary: Per-application output options broken in Audio Volume widget Product: plasma-pa Version: unspecified Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: applet Assignee: now...@gmail.com Reporter: c.t.blak...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Created attachment 132375 --> https://bugs.kde.org/attachment.cgi?id=132375=edit Screenshot SUMMARY Per-application sink and source setting in the Audio Volume widget cannot be accessed, clicking the gear button does nothing. This occurs since upgrade to KDE 5.20. STEPS TO REPRODUCE 1. Open Audio Volume applet widget from system tray 2. Switch to Applications tab 3. Click the gear associated with any running application OBSERVED RESULT The button changes shade as though it was clicked, but no menu appears. EXPECTED RESULT Drop-down menu exposing available sinks for outputs and sources for inputs SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux 5.8.13 (available in About System) KDE Plasma Version: 5.20 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION See attached screenshot. Functionality works fine through the System Settings module. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 420859] On wayland, mouse cursor is much bigger over Qt5 apps
https://bugs.kde.org/show_bug.cgi?id=420859 Doug changed: What|Removed |Added CC||dougjsha...@gmail.com --- Comment #6 from Doug --- I have my cursor set to 24 pt, and my scaling to 150%. On Firefox: In the window it is displaying the cursor at 24 pts (properly) On the title bar it is displaying at 36 pts On Falcon In the window it is displaying at 48 pts On the title bar it is displaying at 36 pts On the desktop it is displaying at 48 pts On Latte Dock it is displaying at 48 pts -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427733] Use new system fonts to improve CJK letter readability under Windows
https://bugs.kde.org/show_bug.cgi?id=427733 --- Comment #2 from Tyson Tan --- Created attachment 132374 --> https://bugs.kde.org/attachment.cgi?id=132374=edit Krita 4.4 CJK UI letter display under Linux This is how Krita 4.4 CJK UI letters look under Linux. The anti-aliasing works properly, provided better readability. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427733] Use new system fonts to improve CJK letter readability under Windows
https://bugs.kde.org/show_bug.cgi?id=427733 --- Comment #1 from Tyson Tan --- Created attachment 132373 --> https://bugs.kde.org/attachment.cgi?id=132373=edit Krita 4.4 CJK UI letter display under Windows 10 This is how Krita 4.4's CJK UI letters look under Windows 10 2004. The letters in on the Blending Mode droplist are difficult to read. They are not big enough to use anti-aliasing, while also not pixel-exact to their bitmap sizes, so they got crushed. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427733] New: Use new system fonts to improve CJK letter readability under Windows
https://bugs.kde.org/show_bug.cgi?id=427733 Bug ID: 427733 Summary: Use new system fonts to improve CJK letter readability under Windows Product: krita Version: 4.4.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: General Assignee: krita-bugs-n...@kde.org Reporter: tyson...@tysontan.com Target Milestone: --- When Krita is set to use a CJK (Chinese, Japanese, Korean) locale, Qt fallbacks to use ancient Windows XP era font sets. These are bitmap, serif fonts. They requires certain letter size (12px) to be pixel exact, and do not work well with sub-pixel anti-aliasing, making them a poor choice for Krita. I will attach screenshots later to showcase what I mean. Since Windows 7, Microsoft ships a new series of UI font sets. They are: Latin default: Segoe UI Simplified Chinese: Microsoft YaHei UI Traditional Chinese: Microsoft JhengHei UI Japanese: Yu Gothic UI Korean: Malgun Gothic These are sans-serif, vector fonts. They scale nicely regardless of their size. I wonder if we can specify these fonts respectively to each CJK locale, or at least add them to qt's fallback font list. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 426260] NVIDIA Optimus: Plasma boots a black desktop on multi-screen setup; wallpaper returns after changing display setup
https://bugs.kde.org/show_bug.cgi?id=426260 --- Comment #8 from Andrés B.S. --- Created attachment 132372 --> https://bugs.kde.org/attachment.cgi?id=132372=edit journalctl and dmesg output journalctl was captured about 30 minutes before posting this. (the issue happened again that boot). I booted the system around 20:50, and hope these logs might shed some light on what's going on. Current versions: Operating System: openSUSE Leap 15.2 KDE Plasma Version: 5.18.5 KDE Frameworks Version: 5.71.0 Qt Version: 5.12.7 Kernel Version: 5.3.18-lp152.44-default -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427725] Kwin maybe crashes Emacs gui
https://bugs.kde.org/show_bug.cgi?id=427725 Alex Belits changed: What|Removed |Added CC||abel...@nyx.net --- Comment #1 from Alex Belits --- This is not related to kwin, this is a regression in color handling in X11 resources. There was an option in KCM that extends color settings to non-KDE applications by setting X resources. Now, in KDE 5.20, it was removed, and resources are set unconditionally. For some reason the mechanism enables resources with generic color names but never sets the values for those, so programs that take color configuration from X resources end up with undefined color names. KDE should either always set resource values for colors BACKGROUND and WINDOW_FOREGROUND that it mentions (ex: "*.WINDOW_FOREGROUND: black"), or not set resources with those values at all. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427732] Tarball contains build directory
https://bugs.kde.org/show_bug.cgi?id=427732 Widya Walesa changed: What|Removed |Added OS|Linux |All -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427732] New: Tarball contains build directory
https://bugs.kde.org/show_bug.cgi?id=427732 Bug ID: 427732 Summary: Tarball contains build directory Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: walech...@gmail.com Target Milestone: --- Created attachment 132371 --> https://bugs.kde.org/attachment.cgi?id=132371=edit Systemsettings 5.20 tarball content SUMMARY Systemsettings tarball source seems have unneeded build directory and must be removed before building the source. STEPS TO REPRODUCE 1. Download tarball source from any mirror, eg. https://download.kde.org/stable/plasma/5.20.0/systemsettings-5.20.0.tar.xz 2. Untar the tarball OBSERVED RESULT Some build script is using staging dir named build, and this condition makes the build script stop. EXPECTED RESULT Tarball source should not contain unneeded directory like build. SOFTWARE/OS VERSIONS Linux/KDE Plasma: All KDE Plasma Version: 5.20 -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427731] Avatar user do not change!
https://bugs.kde.org/show_bug.cgi?id=427731 --- Comment #1 from RYDeN --- https://youtu.be/715Z7Uf7VHU -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427731] New: Avatar user do not change!
https://bugs.kde.org/show_bug.cgi?id=427731 Bug ID: 427731 Summary: Avatar user do not change! Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_users Assignee: uhh...@gmail.com Reporter: ryde...@hotmail.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY When changing my user avatar, as you can see in the attached video, changes do not apply with preset ones. Changes only occur when adding my own images. (At least in kikoff). On the other hand, in the loggin screen, the avatar never changes, neither presets images, nor own ones. STEPS TO REPRODUCE 1. Open user settings 2. Click to change user avatar. 3. Select a preset image. 4. Apply changes. OBSERVED RESULT 1. Click on kikoff. 2. You see the old avatar, also after logoff or restarting. 3. Restart your PC, in the loggin screen you always see the old avatar. EXPECTED RESULT See changes applied in both; kikoff and loggin screen. SOFTWARE/OS VERSIONS Operating System: KDE neon 5.20 KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 Kernel Version: 5.4.0-51-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i7-2600K CPU @ 3.40GHz Memory: 7.7 GiB of RAM Graphics Processor: AMD PITCAIRN -- You are receiving this mail because: You are watching all bug changes.
[SeExpr] [Bug 427651] Static linking of LLVM libs breaks krita
https://bugs.kde.org/show_bug.cgi?id=427651 --- Comment #3 from amyspark --- FTR, linking against shared LLVM makes it impossible to use in systems that provide only static LLVM (like the Academy Software Foundation's Docker images, which I use for testing my changes in CI). I'm checking if the CMake modules provides any tooling to dynamically detect and use the shared lib if available (otherwise, I'll have to use llvm-config...) -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 362189] a11y: Keyboard (caret) tracking for the Zoom feature
https://bugs.kde.org/show_bug.cgi?id=362189 --- Comment #21 from Jos Wijdeven --- Hah, that's better. Looks great so far. Few weird things but that might be the VM. I'll try it on bare metal later this week. Thanks!! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427717] KDEConnect crush on notification
https://bugs.kde.org/show_bug.cgi?id=427717 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- Judging by the backtrace you clicked on the notification before it crashed. Do you remember if you clicked on a specific action or just the notification itself? Also, what desktop are you using? I have an idea what is going on, but I haven't tried to reproduce it yet -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 419176] Keyboard shortcut meta+tab only allows one tab per meta, while alt+tab allows repeated presses of tab
https://bugs.kde.org/show_bug.cgi?id=419176 Keith changed: What|Removed |Added CC||keithhacks-kde...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427730] Meta+Tab results in additional "Tab"s
https://bugs.kde.org/show_bug.cgi?id=427730 Keith changed: What|Removed |Added CC||keithhacks-kde...@yahoo.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427730] New: Meta+Tab results in additional "Tab"s
https://bugs.kde.org/show_bug.cgi?id=427730 Bug ID: 427730 Summary: Meta+Tab results in additional "Tab"s Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keys Assignee: k...@michael-jansen.biz Reporter: keithhacks-kde...@yahoo.com CC: plasma-b...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. Go to Settings -> Shortcuts. 2. Edit a shortcut and click the button to make a new key binding. 3. Press Meta+Tab. OBSERVED RESULT The shortcut is bound to "Meta+Tab,Tab,Tab". EXPECTED RESULT The shortcut is bound to "Meta+Tab". SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: 5.20 (available in About System) KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426640] Kdenlive 20.08.1 freezes when opening some projects created by 19.08.1 but not others
https://bugs.kde.org/show_bug.cgi?id=426640 --- Comment #11 from ahii...@gmail.com --- Tried it with build 546 as well. Same as above. 1.kdenlive and 3.kdenlive load successfully. But with 2.kdenlive, kdenlive freezes during the load, and then a short while later, the kdenlive process terminates. -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426640] Kdenlive 20.08.1 freezes when opening some projects created by 19.08.1 but not others
https://bugs.kde.org/show_bug.cgi?id=426640 --- Comment #10 from ahii...@gmail.com --- Created attachment 132370 --> https://bugs.kde.org/attachment.cgi?id=132370=edit Debug output when opening projects with nightly build 544 I tried it with build 544. My 1.kdenlive and 3.kdenlive load successfully now, and I can confirm that playback in the timeline works as expected without any freezing. My 2.kdenlive still crashes when I try to open it, though. When I tried running it through gdb, it shows the same segfault error last time, in avcodec_flush_buffers() from bin\avcodec-58.dll. When I try to open 2.kdenlive in 19.08.1, it opens fine, so I don't think the project file is corrupt or anything like that. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 427722] Kalarm disabling active alarms calendar on logout when minimized to tray
https://bugs.kde.org/show_bug.cgi?id=427722 David Jarvie changed: What|Removed |Added Status|REPORTED|CONFIRMED Severity|normal |major Ever confirmed|0 |1 --- Comment #2 from David Jarvie --- Thank you for providing sufficient details on how to reproduce this bug, which has helped me to confirm it. Given its importance, it should definitely be fixed in time for KDE apps release 20.08.3. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427729] New: Change theme with "use desktop layout theme" renders desktop to black screen
https://bugs.kde.org/show_bug.cgi?id=427729 Bug ID: 427729 Summary: Change theme with "use desktop layout theme" renders desktop to black screen Product: plasmashell Version: master Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Global Theme packages Assignee: plasma-b...@kde.org Reporter: adelinoara...@adelinoaraujo.com CC: plasma-b...@kde.org Target Milestone: 1.0 SUMMARY updated to 5.20, rebooted, changed the theme for some I can't remember what it was, because I had a few installed. But the problem is to change the theme and select the option "use desktop layout theme". Every time I selected this option when changing theme, I always noticed that the Super key was disabled. This time, I choose "use desktop layout theme" just to see if this was fixed and it was a total crash. STEPS TO REPRODUCE 1. select (almost) any theme with "use desktop layout theme" 2. apply 3. desktop theme changes and 2 seconds later disappears; desktop is a dark, nothing on it OBSERVED RESULT both monitors are black, nothing on screen, no icons, no taskbar, no menus, no right-click menus, nothing EXPECTED RESULT theme was applied and kept running plasma with the new theme SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: ArchLinux - 5.20 (available in About System) KDE Plasma Version: 5.20 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION I cannot figure out what was the theme but this problem was on previous versions of plasma, but before I always lost the taskbar and Super key, but I managed to open systemsettings and change to Breeze and recover. This time, even if you change the systemsettings back to another theme with "use dekstop layout theme" and reboot, the desktop appears, the taskbar appears for 2 seconds and it's gone. I end up with a black screen. I also tried to edit some settings file to start plasma with breeze theme but nothing, it start with the theme that broke Plasma, that has the taskbar on top. Plasma should make sure that the theme is applied and it is working. At least had a terminal option to start over with the default settings, so we could recover from this critical situation. I managed to reboot and change some files by using another session ctrl+alt+f2 or f3. I also had xfce4 installed that I used to try to edit some files I found on .config but I could not find a single place where it says what files are the configuration of plasma. This is not the first time that changing themes breaks plasma, but once again I will install plasma again soon as I backup my docs. Selected critical severity because it renders the computer to blank. -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 427650] kactivitymanagerd crashes with segmentation fault
https://bugs.kde.org/show_bug.cgi?id=427650 Albert changed: What|Removed |Added CC||anonis...@yahoo.com --- Comment #2 from Albert --- that patch fixed it for me -- You are receiving this mail because: You are watching all bug changes.
[kactivitymanagerd] [Bug 426963] kactivitymanagerd continuously crashing
https://bugs.kde.org/show_bug.cgi?id=426963 Albert changed: What|Removed |Added CC||anonis...@yahoo.com --- Comment #9 from Albert --- https://bugs.kde.org/show_bug.cgi?id=427650#c1 that patch fixed it for me -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 273720] wish: specify defer interval in the alarm
https://bugs.kde.org/show_bug.cgi?id=273720 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #2 from David Jarvie --- I'm reluctant to add extra complexity to the alarm edit dialog in order to set the default defer interval for individual alarms. I'm not convinced that it would be commonly enough used to justify doing this. Two features in KAlarm provide partial control over defer intervals, even if they don't provide exactly what you request: 1) The default defer interval common to all alarms can be set in KAlarm's preferences. 2) Whenever an alarm is deferred, the selected deferral interval is saved as the default for future recurrences of that alarm. So, instead of setting its defer interval when you create an alarm, you actually set it the first time you defer the alarm. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 275527] Snooze toolbar button
https://bugs.kde.org/show_bug.cgi?id=275527 Bug 275527 depends on bug 273720, which changed state. Bug 273720 Summary: wish: specify defer interval in the alarm https://bugs.kde.org/show_bug.cgi?id=273720 What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 427728] New: Window size
https://bugs.kde.org/show_bug.cgi?id=427728 Bug ID: 427728 Summary: Window size Product: kate Version: 20.08.2 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: leonei...@gmail.com Target Milestone: --- Created attachment 132369 --> https://bugs.kde.org/attachment.cgi?id=132369=edit resizing kate SUMMARY Cant resize Kate window less than: W169 x H301 it is useful having a notepad window as a "single line height" or as a "single col width". Just see the attached image. Lost too much space. STEPS TO REPRODUCE 1. Just try to resize kate less than W169 x H301 OBSERVED RESULT There is a limit to resize. Kate window still big EXPECTED RESULT Resize less than width:169 or height:301 SOFTWARE/OS VERSIONS Operating System: Kubuntu 20.10 KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.14.2 Kernel Version: 5.8.0-23-generic OS Type: 64-bit Processors: 8 × Intel® Core™ i5-8250U CPU @ 1.60GHz Memory: 7.7 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 422795] Video is laggy in Kamoso, but smooth in BigBlueButton
https://bugs.kde.org/show_bug.cgi?id=422795 --- Comment #4 from Aleix Pol --- My best guess so far is that gstreamer/camerabin (the component we share with cheese) is slow. No idea about zoom. I can see it sometimes too (not always !?). If you want to test with a surely different implementation, you can check OBS. It's also Qt but it doesn't use gstreamer. -- You are receiving this mail because: You are watching all bug changes.
[KAccounts] [Bug 426034] Trying to add Google account brings me back to the accounts overview
https://bugs.kde.org/show_bug.cgi?id=426034 tiagomari...@gmail.com changed: What|Removed |Added CC||tiagomari...@gmail.com --- Comment #1 from tiagomari...@gmail.com --- I'm having this same results described on KDE neon. Linux/KDE Plasma: KDE neon 5.20 KDE Plasma Version: 5.20.0 KDE Framework Version: 5.75.0 Qt Version: 5.15.0 Kernel Version: 5.4.0-51-generic -- You are receiving this mail because: You are watching all bug changes.
[Plasma SDK] [Bug 427727] New: Error in execute idle-python3.8
https://bugs.kde.org/show_bug.cgi?id=427727 Bug ID: 427727 Summary: Error in execute idle-python3.8 Product: Plasma SDK Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: plasma-b...@kde.org Reporter: lmontalv...@gmail.com CC: antonis.tsiapalio...@kde.org Target Milestone: --- Created attachment 132368 --> https://bugs.kde.org/attachment.cgi?id=132368=edit Code of error idle-python3.8 SUMMARY Error in execute idle-python3.8 after update to plasma 3.20 STEPS TO REPRODUCE 1. I execute idle-python.3.8 2. Don't show the window OBSERVED RESULT The error appear in file attachment EXPECTED RESULT SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE plasma Neon 5.20 User Edition (available in About System) KDE Plasma Version: 5.20 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION Version 64 bits -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427726] New: Test Mode option for SSDM KCM
https://bugs.kde.org/show_bug.cgi?id=427726 Bug ID: 427726 Summary: Test Mode option for SSDM KCM Product: systemsettings Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_sddm Assignee: k...@davidedmundson.co.uk Reporter: xenoida...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- Even though we have the screenshot thumbnail for each SDDM theme, it would be handy to have a test button in KCM to run the command: $ sddm-greeter --test-mode --theme /usr/share/sddm/themes/breeze/ This concept already exists for the Plasma Splashscreens. Thank you -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 427725] New: Kwin maybe crashes Emacs gui
https://bugs.kde.org/show_bug.cgi?id=427725 Bug ID: 427725 Summary: Kwin maybe crashes Emacs gui Product: kwin Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: perfinst...@gmail.com Target Milestone: --- SUMMARY I use kde Neon user, trying emacs with gui I noticed that it crashes and from terminal it reports: emacs Undefined color: "WINDOW_FOREGROUND" ... can only be used with emacs -nw, how to start emacs-gtk gui? STEPS TO REPRODUCE 1.I write emacs from terminal 2. returns the error:Undefined color: "WINDOW_FOREGROUND" OBSERVED RESULT crash SOFTWARE/OS VERSIONS Linux/KDE Plasma: kde Neon user 5.20 (available in About System) KDE Plasma Version: 5.20 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.0 ADDITIONAL INFORMATION it only happens with kde neon, not with ubuntu, not with kubuntu (tested by virtualbox), and said by others not by arch with kde -- You are receiving this mail because: You are watching all bug changes.
[klipper] [Bug 427724] New: Klipper needs a privacy mode
https://bugs.kde.org/show_bug.cgi?id=427724 Bug ID: 427724 Summary: Klipper needs a privacy mode Product: klipper Version: 5.19.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: plasma-widget Assignee: plasma-b...@kde.org Reporter: m...@naraesk.eu Target Milestone: --- SUMMARY Klipper logs your selection history. Currently, it is possible to delete individual entries. But this can be a lot of work. It would be great if Klipper gets a private mode where no new entries are added. You should be able to activate it via the Plasma Widget with one or two clicks. This feature request is related to https://bugs.kde.org/show_bug.cgi?id=391046. But the private mode should work independently from private activities. SOFTWARE/OS VERSIONS LOperating System: Arch Linux KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.8.14-arch1-1 OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 --- Comment #6 from Franco Pellegrini --- I'm using cpu, ram, disk and net. The only with this problem is net. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427723] New: Disable mouse hover automatic selection in Kicker menu
https://bugs.kde.org/show_bug.cgi?id=427723 Bug ID: 427723 Summary: Disable mouse hover automatic selection in Kicker menu Product: plasmashell Version: 5.19.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Menu (Kicker) Assignee: h...@kde.org Reporter: med.medin.2...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 132367 --> https://bugs.kde.org/attachment.cgi?id=132367=edit Mouse hover automatic selection in Kicker menu When I open Kicker menu and try to click on any favorite app in far right side or on any system action (leave, lock, poweroff or restart) then the mouse passes over the menu root items which causes automatic selection and trigger the appearance of the sub items. It would be really cool to have an option to disable the automatic selection triggered by mouse hover. See my attached video for more info. Operating System: Manjaro Linux KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 Kernel Version: 5.4.67-1-MANJARO OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[kamoso] [Bug 424193] Viewfinder has a red overlay
https://bugs.kde.org/show_bug.cgi?id=424193 Nafis changed: What|Removed |Added CC||mnabid...@outlook.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 418411] [Wayland] Cursor appears as a black box.
https://bugs.kde.org/show_bug.cgi?id=418411 --- Comment #7 from Stefan K. --- I can report the bug is gone. The cursor is now working as expected. It seems to be fixed in September - my best guess. KDE (Neon) is Kernel 5.8, Plasma 5.19.5, Qt 5.15 and KF 5.75. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk --- Comment #5 from David Edmundson --- Just to confirm, the other sensors are still updating? -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 408493] Desktop briefly visible before lock screen appears
https://bugs.kde.org/show_bug.cgi?id=408493 Patrick Silva changed: What|Removed |Added CC||kingspammernerd@protonmail. ||com --- Comment #3 from Patrick Silva --- *** Bug 414414 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 408493] Desktop briefly visible before lock screen appears
https://bugs.kde.org/show_bug.cgi?id=408493 Patrick Silva changed: What|Removed |Added CC||kos...@koshka.ddns.net --- Comment #2 from Patrick Silva --- *** Bug 415362 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 427718] Gwenview does not start
https://bugs.kde.org/show_bug.cgi?id=427718 Antonio Rojas changed: What|Removed |Added CC||aro...@archlinux.org Resolution|FIXED |DOWNSTREAM --- Comment #4 from Antonio Rojas --- (In reply to Christoph Feck from comment #2) > So libraw removed a symbol without bumping the .so version? Yes https://github.com/LibRaw/LibRaw/issues/350 -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 415362] Lock after waking from sleep: a glimpse of desktop before lock screen appears.
https://bugs.kde.org/show_bug.cgi?id=415362 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #3 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 408493 *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 414414] KDE (Wayland) Lock screen partially reveals desktop contents before showing password dialog
https://bugs.kde.org/show_bug.cgi?id=414414 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 408493 *** -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 427718] Gwenview does not start
https://bugs.kde.org/show_bug.cgi?id=427718 Francisco Cribari changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution|--- |FIXED -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 427718] Gwenview does not start
https://bugs.kde.org/show_bug.cgi?id=427718 --- Comment #3 from Francisco Cribari --- The problem was solved after libkdcraw was upgraded to version 20.08.2-2 on my system. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427685] Notification window closes when going back if no other window is visible
https://bugs.kde.org/show_bug.cgi?id=427685 rLy changed: What|Removed |Added CC||rl...@hotmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 427718] Gwenview does not start
https://bugs.kde.org/show_bug.cgi?id=427718 --- Comment #2 from Christoph Feck --- So libraw removed a symbol without bumping the .so version? -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 427722] Kalarm disabling active alarms calendar on logout when minimized to tray
https://bugs.kde.org/show_bug.cgi?id=427722 --- Comment #1 from David Rosenstrauch --- Created attachment 132366 --> https://bugs.kde.org/attachment.cgi?id=132366=edit Kalarm running with Active Alarms calendar enabled (expected) -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 419142] No login screen after resume from suspend - I have to unlock via TTY2
https://bugs.kde.org/show_bug.cgi?id=419142 Patrick Silva changed: What|Removed |Added CC||silvan.cala...@mambasoft.it --- Comment #9 from Patrick Silva --- *** Bug 421066 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 421066] No password prompt to unlock screen after resume from suspend
https://bugs.kde.org/show_bug.cgi?id=421066 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com --- Comment #5 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 419142 *** -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 427722] New: Kalarm disabling active alarms calendar on logout when minimized to tray
https://bugs.kde.org/show_bug.cgi?id=427722 Bug ID: 427722 Summary: Kalarm disabling active alarms calendar on logout when minimized to tray Product: kalarm Version: 3.0.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: djar...@kde.org Reporter: dar...@darose.net Target Milestone: --- Created attachment 132365 --> https://bugs.kde.org/attachment.cgi?id=132365=edit Kalarm starting up with Active Alarms calendar disabled SUMMARY I've started noticing an issue with Kalarm recently. (Looks like it may have started when ArchLinux upgraded to KDE 20.08.2) When I log out while Kalarm is minimized to the system tray (thereby forcing Kalarm to close) the next time I log in the "active alarms" calendar is disabled/unchecked. This does not happen when I either a) quit Kalarm manually, or b) when I log out with Kalarm *not* minimized to the tray. This is becoming a bit of a nuisance, since when the active alarms are disabled Kalarm doesn't pop up any alarm windows notifying me about appointments. As I normally start up kalarm minimized to the tray (and generally keep it minimized), I'm running into this problem frequently. STEPS TO REPRODUCE 1. Start Kalarm, minimize it to the tray. 2. Log out. (Of the XFCE desktop, in my case.) 3. Log back in, and start Kalarm again. OBSERVED RESULT Kalarm starts with the Active Alarms calendar disabled/unchecked. (I can also see in the ~/.config/kalarmresources file that it contains "Enabled=".) EXPECTED RESULT Kalarm should start with the Active Alarms calendar enabled and active. (And ~/.config/kalarmresources file should contain "Enabled=Active".) This happens both on my main account, as well as on a brand new test account that I set up just for this purpose. (So it's not an issue related to my user configuration.) SOFTWARE/OS VERSIONS Kalarm version: 3.0.2 Windows: n/a macOS: n/a *** *** NOTE: I AM USING Kalarm WITH THE XFCE DESKTOP ENVIRONMENT, NOT KDE *** *** Linux/KDE Plasma: Version 3.0.2 (KDE Apps 20.08.2) KDE Plasma Version: 5.20.0 KDE Frameworks Version: ? Qt Version: 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427721] New: System wide copy paste
https://bugs.kde.org/show_bug.cgi?id=427721 Bug ID: 427721 Summary: System wide copy paste Product: plasmashell Version: 5.19.5 Platform: Manjaro OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: med.medin.2...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 It would be practical and preferable to keep the copied items even if the source application is closed. Many times I copy files from Dolphin then close it and when I try to paste them on my Desktop it fails because the copied items are deleted after Dolphin is closed. This happens also when I copy some code from Kate and close it, and the paste operation fails on another IDE like Eclipse or VSCode. Operating System: Manjaro Linux KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 Kernel Version: 5.4.67-1-MANJARO OS Type: 64-bit -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427720] EXR files imported as file layers generate canvas-wide layers filled with black
https://bugs.kde.org/show_bug.cgi?id=427720 --- Comment #1 from to...@offensivelytolerant.com --- Created attachment 132364 --> https://bugs.kde.org/attachment.cgi?id=132364=edit picture showing what the issue looks like (with a test file using only the EXR external file) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 427720] New: EXR files imported as file layers generate canvas-wide layers filled with black
https://bugs.kde.org/show_bug.cgi?id=427720 Bug ID: 427720 Summary: EXR files imported as file layers generate canvas-wide layers filled with black Product: krita Version: 4.4.0 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: File formats Assignee: krita-bugs-n...@kde.org Reporter: to...@offensivelytolerant.com Target Milestone: --- Created attachment 132363 --> https://bugs.kde.org/attachment.cgi?id=132363=edit Archive containing the issue demonstration file SUMMARY When imported as File Layers, EXR files smaller than the picture itself will appear in the top-left corner, as usual, but since the 4.4.0 release, all empty space will be filled with black colour to match the size of the canvas, generating very large layers filled with unneeded information. STEPS TO REPRODUCE 1. Unpack the FileLayerFillIssue.zip, which contains a .kra file and two small external files used as File Layer, pinkSquare.exr and pinkSquare.png. 2. Open the FileLayerFillIssue.kra file with Krita 4.3 ; the file layers are in the corner of the picture and background is still visible. 3. Open the FileLayerFillIssue.kra file with Krita 4.4 ; the file layers are in the corner of the picture, but background is not visible as the file layer referencing pinkSquare.exr filled all the canvas with opaque black. Layer thumbnail shows that this layer is now as large as the canvas itself ( Krita4_4FileLayerBehaviour.png shows a side-by-side comparison with the background using only the EXR file layer) OBSERVED RESULT File layer referencing the EXR external picture file introduced black opaque pixels in the empty space not covered by the picture file itself EXPECTED RESULT File layer referencing the EXR external picture file should left most of the picture empty, as does the file layer referencing the PNG external picture file SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Parabola Linux (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.
[klipper] [Bug 427713] Plasma 5.20 - Clipboard not working on Wayland
https://bugs.kde.org/show_bug.cgi?id=427713 Till Schäfer changed: What|Removed |Added CC||till2.schaefer@uni-dortmund ||.de -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 427718] Gwenview does not start
https://bugs.kde.org/show_bug.cgi?id=427718 Kan changed: What|Removed |Added Status|REPORTED|CONFIRMED CC||kande...@hotmail.com Ever confirmed|0 |1 --- Comment #1 from Kan --- Same issue with two of my systems. The culprit is libraw, downgrading to libraw-0.20.0-1 fixed the issue, temporarily. Placing libraw on hold from upgrades until a proper fix is submitted. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 426902] Unlock fails even with correct password
https://bugs.kde.org/show_bug.cgi?id=426902 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #8 from Patrick Silva --- I noticed this problem on neon unstable today. Then I typed my pasword with the virtual keyboard and my screen was unlocked as expected. -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 426902] Unlock fails even with correct password
https://bugs.kde.org/show_bug.cgi?id=426902 Patrick Silva changed: What|Removed |Added CC||jumper.l...@gmail.com --- Comment #7 from Patrick Silva --- *** Bug 427254 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kscreenlocker] [Bug 427254] Unlocking Failed
https://bugs.kde.org/show_bug.cgi?id=427254 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #3 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 426902 *** -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 406472] Edit metadata from within Elisa
https://bugs.kde.org/show_bug.cgi?id=406472 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #4 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/multimedia/elisa/-/merge_requests/178 -- You are receiving this mail because: You are watching all bug changes.
[elisa] [Bug 427719] New: Cover Art Not Displaying for Tracks with No Album Meta Data.
https://bugs.kde.org/show_bug.cgi?id=427719 Bug ID: 427719 Summary: Cover Art Not Displaying for Tracks with No Album Meta Data. Product: elisa Version: 20.08.1 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: nwestervelt...@gmail.com Target Milestone: --- SUMMARY Cover art for tracks with no album meta data don't display their cover art. STEPS TO REPRODUCE 1. Disable the baloo file indexer. 2. Put a track without album meta data in your Music folder. 3. Open Elisa and browse to the added track. OBSERVED RESULT The green cd placeholder is seen in place of the cover art, to the left of the track's name in the 'Tracks' menu. EXPECTED RESULT The cover art displays where expected, left of the track's name in the 'Tracks' menu. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE Tumbleweed 20201009 (available in About System) KDE Plasma Version: 5.19.5 KDE Frameworks Version: 5.74.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION The tracks that are affected are too large to be attached directly, so here's a link to one of them in my google drive: https://drive.google.com/file/d/1tt4Mp_aibPCWnQ7kTznoKjhjLmVOO7uS/view?usp=sharing -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426048] Changing a clip's speed causes a crash
https://bugs.kde.org/show_bug.cgi?id=426048 Vincent PINON changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #5 from Vincent PINON --- mlt commit 9499802f on 09.05 adresses cases of low speed crashing. can you test with 20.08.2 appimage? -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 425305] mis-positioned weather icon in system tray
https://bugs.kde.org/show_bug.cgi?id=425305 Patrick Silva changed: What|Removed |Added CC||ievgenso...@gmail.com --- Comment #1 from Patrick Silva --- *** Bug 427679 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdeplasma-addons] [Bug 427679] Weather configured in system tray overlaps with next item in the system tray
https://bugs.kde.org/show_bug.cgi?id=427679 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #4 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 425305 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426494] kdenlive crashing trying to remove an effect
https://bugs.kde.org/show_bug.cgi?id=426494 Vincent PINON changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #1 from Vincent PINON --- Sorry but the crash shows a problem in the Kvantum Qt Widget styling lib. Can't do anything for this in Kdenlive -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 426493] swr_convert() failed when restoring audio
https://bugs.kde.org/show_bug.cgi?id=426493 Vincent PINON changed: What|Removed |Added Resolution|--- |UPSTREAM Status|REPORTED|RESOLVED --- Comment #4 from Vincent PINON --- the resampling is needed for speed change. the speed effect is implemented in MLT & ffmpeg 4000% speed change is uncommon, probably it leads to unexpected situations sorry but I can't track down this bug -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 Patrick Silva changed: What|Removed |Added CC||mike.cloa...@gmail.com --- Comment #4 from Patrick Silva --- *** Bug 427693 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 427693] System Monitor Sensor 1.0 does not retain interfaces after logout in plasma 5.20
https://bugs.kde.org/show_bug.cgi?id=427693 Patrick Silva changed: What|Removed |Added Resolution|--- |DUPLICATE CC||bugsefor...@gmx.com Status|REPORTED|RESOLVED --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 425992 *** -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 427701] Can't change wallpaper type in screen locking
https://bugs.kde.org/show_bug.cgi?id=427701 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com --- Comment #1 from Patrick Silva --- Same thing on neon unstable. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 425992] Network Speed widget is not working on neon unstable
https://bugs.kde.org/show_bug.cgi?id=425992 Patrick Silva changed: What|Removed |Added CC||francogpellegr...@gmail.com --- Comment #3 from Patrick Silva --- *** Bug 427710 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 427279] Choma Key, Position And zoom And many effects are not working correctly please do something.
https://bugs.kde.org/show_bug.cgi?id=427279 Vincent PINON changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #1 from Vincent PINON --- Many issues affected 20.08.1 on Windows (comma separator for floating points?) Please tell us if 20.08.2 fixed the problem -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 427710] widget not showing data, flat line only
https://bugs.kde.org/show_bug.cgi?id=427710 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED CC||bugsefor...@gmx.com Resolution|--- |DUPLICATE --- Comment #1 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 425992 *** -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 406811] first 23 frames of freeze effect render as blank white
https://bugs.kde.org/show_bug.cgi?id=406811 Vincent PINON changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|CONFIRMED |NEEDSINFO --- Comment #12 from Vincent PINON --- please report if OK for you :) -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 389952] 360°-Transformation (conversion of projection)
https://bugs.kde.org/show_bug.cgi?id=389952 Vincent PINON changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 427097] Render bug, preview ok, but render is not syncronized objects in timeline and effects bug to.
https://bugs.kde.org/show_bug.cgi?id=427097 Vincent PINON changed: What|Removed |Added Resolution|--- |WAITINGFORINFO Status|REPORTED|NEEDSINFO --- Comment #2 from Vincent PINON --- Please confirm if parallel processing was the issue -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 388709] Error message when ffmpeg, melt, ... can't be find
https://bugs.kde.org/show_bug.cgi?id=388709 Vincent PINON changed: What|Removed |Added Version Fixed In||20.08.3 Resolution|--- |FIXED Latest Commit||b7ab436a3c66eff2aa090a46096 ||c92e8dc33ed26 Status|REPORTED|RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 414701] Kinetic scrolling breaks Back and Forward navigation
https://bugs.kde.org/show_bug.cgi?id=414701 --- Comment #8 from Rodolfo Panerai --- Well, I ended up bisecting it. The offending commit is bdb2df773d774c15cf0a17fcae198d3f2452cdfa (Fix forms when inertially scrolling). https://invent.kde.org/graphics/okular/commit/bdb2df773d774c15cf0a17fcae198d3f2452cdfa Curiously, it reverts the change to the same line in ui/pageview.cpp that was fixed by commit 09cb524f1753ca1c9272618f9ceaded4c8ed7cb4 mentioned earlier in this bugreport (same author). -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 426502] Okular occasionally crashes when opening PDF files
https://bugs.kde.org/show_bug.cgi?id=426502 Ben Bullard changed: What|Removed |Added CC||benbullar...@cox.net -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 419480] Crashed during scaling or bolding
https://bugs.kde.org/show_bug.cgi?id=419480 --- Comment #2 from Lonnie --- Why has this been marked a duplicate of a bug for "adding new column"? Adding columns is NOT what I've reported above. -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 427718] Gwenview does not start
https://bugs.kde.org/show_bug.cgi?id=427718 Francisco Cribari changed: What|Removed |Added CC||crib...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 427718] New: Gwenview does not start
https://bugs.kde.org/show_bug.cgi?id=427718 Bug ID: 427718 Summary: Gwenview does not start Product: gwenview Version: 20.08.2 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: crib...@gmail.com Target Milestone: --- SUMMARY I run Arch Linux and KDE Plasma 5.20. I am unable to start gwenview. The version of gwenview in my system is 20.08.2. STEPS TO REPRODUCE 1. Try to start gwenview 2. 3. OBSERVED RESULT Gwenview does not start. The error message: gwenview: symbol lookup error: /usr/lib/libKF5KDcraw.so.5: undefined symbol: _ZN6LibRaw11open_bufferEPvm EXPECTED RESULT Gwenview should start. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch Linux, KDE Plasma 5.20 (available in About System) KDE Plasma Version: 5.20 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[calligrasheets] [Bug 391018] Crash after adding new column in Calligra Sheets
https://bugs.kde.org/show_bug.cgi?id=391018 Luke-Jr changed: What|Removed |Added Version|unspecified |3.2.1 CC||luke-jr+kdeb...@utopios.org --- Comment #10 from Luke-Jr --- With 3.2.1 (only version in Gentoo), adding a new row above a row I just added crashes every time. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 427717] New: KDEConnect crush on notification
https://bugs.kde.org/show_bug.cgi?id=427717 Bug ID: 427717 Summary: KDEConnect crush on notification Product: kdeconnect Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: common Assignee: albertv...@gmail.com Reporter: misha10...@yandex.ru Target Milestone: --- Application: kdeconnectd (1.4.0) Qt Version: 5.14.2 Frameworks Version: 5.73.0 Operating System: Linux 5.8.13-200.fc32.x86_64 x86_64 Windowing system: X11 Distribution: Fedora 32 (Thirty Two) -- Information about the crash: - What I was doing when the application crashed: Crashed a few times when I am getting notification from phone (version 1.14.2, installed from Google Play) from Telegram Telegram is opened on my phone and computer at the same time Possibly it's because telegram removes notifications from phone when I open this message on computer Fedora 32 LXDE The crash can be reproduced sometimes. -- Backtrace: Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7ff1679df900 (LWP 37675))] Thread 4 (Thread 0x7ff155970700 (LWP 37679)): #0 0x7ff166448bed in g_source_unref_internal () from /lib64/libglib-2.0.so.0 #1 0x7ff16644a945 in g_source_iter_next () from /lib64/libglib-2.0.so.0 #2 0x7ff16644bee3 in g_main_context_prepare () from /lib64/libglib-2.0.so.0 #3 0x7ff16644c9db in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #4 0x7ff16644cbe3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #5 0x7ff167e78b8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #6 0x7ff167e2b91b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #7 0x7ff167c97427 in QThread::exec() () from /lib64/libQt5Core.so.5 #8 0x7ff167c98690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #9 0x7ff166db3432 in start_thread () from /lib64/libpthread.so.0 #10 0x7ff167913913 in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7ff156171700 (LWP 37678)): #0 0x7ff167908aaf in poll () from /lib64/libc.so.6 #1 0x7ff16644caae in g_main_context_iterate.constprop () from /lib64/libglib-2.0.so.0 #2 0x7ff16644cbe3 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x7ff167e78b8b in QEventDispatcherGlib::processEvents(QFlags) () from /lib64/libQt5Core.so.5 #4 0x7ff167e2b91b in QEventLoop::exec(QFlags) () from /lib64/libQt5Core.so.5 #5 0x7ff167c97427 in QThread::exec() () from /lib64/libQt5Core.so.5 #6 0x7ff16810b51b in QDBusConnectionManager::run() () from /lib64/libQt5DBus.so.5 #7 0x7ff167c98690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #8 0x7ff166db3432 in start_thread () from /lib64/libpthread.so.0 #9 0x7ff167913913 in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7ff156991700 (LWP 37677)): #0 0x7ff167908aaf in poll () from /lib64/libc.so.6 #1 0x7ff165eb738a in _xcb_conn_wait () from /lib64/libxcb.so.1 #2 0x7ff165eb971a in xcb_wait_for_event () from /lib64/libxcb.so.1 #3 0x7ff156bc6c78 in QXcbEventQueue::run() () from /lib64/libQt5XcbQpa.so.5 #4 0x7ff167c98690 in QThreadPrivate::start(void*) () from /lib64/libQt5Core.so.5 #5 0x7ff166db3432 in start_thread () from /lib64/libpthread.so.0 #6 0x7ff167913913 in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7ff1679df900 (LWP 37675)): [KCrash Handler] #4 0x7ff167e63e81 in QVariant::QVariant(QString const&) () from /lib64/libQt5Core.so.5 #5 0x7ff155038e6a in void NetworkPacket::set(QString const&, QString const&) () from /usr/lib64/qt5/plugins/kdeconnect/kdeconnect_notifications.so #6 0x7ff155037385 in NotificationsDbusInterface::sendAction(QString const&, QString const&) () from /usr/lib64/qt5/plugins/kdeconnect/kdeconnect_notifications.so #7 0x7ff167e5bf76 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #8 0x7ff15503263e in Notification::actionTriggered(QString const&, QString const&) () from /usr/lib64/qt5/plugins/kdeconnect/kdeconnect_notifications.so #9 0x7ff167e5bf76 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #10 0x7ff169023ef5 in KNotification::activated(unsigned int) () from /lib64/libKF5Notifications.so.5 #11 0x7ff16902a3e4 in KNotificationManager::notificationActivated(int, int) () from /lib64/libKF5Notifications.so.5 #12 0x7ff167e5bf76 in void doActivate(QObject*, int, void**) () from /lib64/libQt5Core.so.5 #13 0x7ff169023fc3 in KNotificationPlugin::actionInvoked(int, int) () from /lib64/libKF5Notifications.so.5 #14 0x7ff16903b4cc in NotifyByPopup::onNotificationActionInvoked(unsigned int, QString const&) () from
[krunner] [Bug 414709] krunner crashed when tried to paste data
https://bugs.kde.org/show_bug.cgi?id=414709 Alexander Lohnau changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #4 from Alexander Lohnau --- Great, it is also fixed for me :) -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 427716] New: When you log in to the site "webdav.yandex.ru" the gwenview app is closing.
https://bugs.kde.org/show_bug.cgi?id=427716 Bug ID: 427716 Summary: When you log in to the site "webdav.yandex.ru" the gwenview app is closing. Product: gwenview Version: 19.12.3 Platform: Ubuntu Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: ipolu...@yandex.ru Target Milestone: --- Application: gwenview (19.12.3) Qt Version: 5.12.8 Frameworks Version: 5.68.0 Operating System: Linux 5.4.0-42-generic x86_64 Windowing system: X11 Distribution: Ubuntu 20.04.1 LTS -- Information about the crash: I enter my username and password, click connect and the app returns an error. The crash can be reproduced every time. -- Backtrace: Application: Gwenview (gwenview), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6cc64c6f80 (LWP 5023))] Thread 8 (Thread 0x7f6cb5e4a700 (LWP 5045)): #0 __GI___libc_read (nbytes=10, buf=0x7f6cb5e4991e, fd=25) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=25, buf=0x7f6cb5e4991e, nbytes=10) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7f6cc79fd955 in pa_read () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #3 0x7f6cc9b9d416 in pa_mainloop_prepare () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f6cc9b9deb4 in pa_mainloop_iterate () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f6cc9b9df70 in pa_mainloop_run () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f6cc9bac11d in ?? () from /usr/lib/x86_64-linux-gnu/libpulse.so.0 #7 0x7f6cc7a2c67c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #8 0x7f6cca51b609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f6ccbe0c103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 7 (Thread 0x7f6cb67fc700 (LWP 5030)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55da08d64818) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55da08d647c8, cond=0x55da08d647f0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55da08d647f0, mutex=0x55da08d647c8) at pthread_cond_wait.c:638 #3 0x7f6cbccb697b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f6cbccb658b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f6cca51b609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f6ccbe0c103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f6cb6ffd700 (LWP 5029)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55da08d64818) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55da08d647c8, cond=0x55da08d647f0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55da08d647f0, mutex=0x55da08d647c8) at pthread_cond_wait.c:638 #3 0x7f6cbccb697b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f6cbccb658b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f6cca51b609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f6ccbe0c103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f6cb77fe700 (LWP 5028)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55da08d64818) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55da08d647c8, cond=0x55da08d647f0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55da08d647f0, mutex=0x55da08d647c8) at pthread_cond_wait.c:638 #3 0x7f6cbccb697b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f6cbccb658b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f6cca51b609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f6ccbe0c103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f6cb7fff700 (LWP 5027)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55da08d64818) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55da08d647c8, cond=0x55da08d647f0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55da08d647f0, mutex=0x55da08d647c8) at pthread_cond_wait.c:638 #3 0x7f6cbccb697b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #4 0x7f6cbccb658b in ?? () from /usr/lib/x86_64-linux-gnu/dri/i965_dri.so #5 0x7f6cca51b609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f6ccbe0c103 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f6cb700 (LWP 5025)): #0 0x7f6ccbdff96f in __GI___poll (fds=0x7f6cb8011cb0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1
[krunner] [Bug 414709] krunner crashed when tried to paste data
https://bugs.kde.org/show_bug.cgi?id=414709 Szőts Ákos changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #3 from Szőts Ákos --- I tried to paste some data now into GMail but KRunner didn't crash this time. -- You are receiving this mail because: You are watching all bug changes.
