[kwin] [Bug 443246] Parts of windows often get cut off in desktop grid effect
https://bugs.kde.org/show_bug.cgi?id=443246 Kishore Gopalakrishnan changed: What|Removed |Added Attachment #142110|Arrangement of windows to |A) Arrangement of windows description|reproduce the bug |to reproduce the bug -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443246] Parts of windows often get cut off in desktop grid effect
https://bugs.kde.org/show_bug.cgi?id=443246 --- Comment #2 from Kishore Gopalakrishnan --- Created attachment 142112 --> https://bugs.kde.org/attachment.cgi?id=142112=edit C) present windows effect shows windows correctly -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443246] Parts of windows often get cut off in desktop grid effect
https://bugs.kde.org/show_bug.cgi?id=443246 --- Comment #1 from Kishore Gopalakrishnan --- Created attachment 142111 --> https://bugs.kde.org/attachment.cgi?id=142111=edit B) Desktop grid shows truncated image of window -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443246] New: Parts of windows often get cut off in desktop grid effect
https://bugs.kde.org/show_bug.cgi?id=443246 Bug ID: 443246 Summary: Parts of windows often get cut off in desktop grid effect Product: kwin Version: 5.22.90 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: effects-window-management Assignee: kwin-bugs-n...@kde.org Reporter: kishor...@gmail.com Target Milestone: --- Created attachment 142110 --> https://bugs.kde.org/attachment.cgi?id=142110=edit Arrangement of windows to reproduce the bug SUMMARY The Desktop Grid effect displays scaled down versions of the windows open on each virtual desktop. These scaled down images are sometimes truncated incorrectly. STEPS TO REPRODUCE 1. Create at least two virtual desktops 2. Tile a window to the right half of the screen (see attached screenshot A) 3. Trigger desktop grid effect OBSERVED RESULT Only part of the window is shown in the Desktop Grid effect (see attached screenshot B). EXPECTED RESULT All windows should be shown correctly in Desktop Grid effect SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.10.70-1-lts (64-bit) Graphics Platform: X11 Processors: 4 × AMD EPYC-Rome Processor Memory: 1.4 GiB of RAM Graphics Processor: virgl (this is a VM, but it is also reproducible on bare metal with AMD graphics) ADDITIONAL INFORMATION 1. Bug is not reproducible if the user is using only one virtual desktop. 2. The Present Windows effect shows the window correctly (see attached screenshot C) -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443245] New: Setting a new recordings directory doesn't take effect until Krita is restarted
https://bugs.kde.org/show_bug.cgi?id=443245 Bug ID: 443245 Summary: Setting a new recordings directory doesn't take effect until Krita is restarted Product: krita Version: 5.0.0-beta1 Platform: Appimage OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Dockers/Recorder Assignee: krita-bugs-n...@kde.org Reporter: tomtomtomreportin...@gmail.com Target Milestone: --- SUMMARY Setting a new recordings directory in the recorder docker doesn't actually take effect until Krita is restarted. STEPS TO REPRODUCE 1. Open the Recorder docker. 2. Select a new recordings directory. 3. Record some strokes. 4. Check the recordings directory that was newly set. OBSERVED RESULT No frames seem to be sent to the newly set directory. The frames are instead sent to the previously set directory. EXPECTED RESULT The new recordings directory should take effect once it's set. If there isn't a way to directly fix this issue, there should at least be some warning somewhere. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Debian sid KDE Plasma Version: 5.21.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.12.11 (Appimage) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 443244] find next/previous icon inconsistence
https://bugs.kde.org/show_bug.cgi?id=443244 qydwhotm...@gmail.com changed: What|Removed |Added CC||qydwhotm...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 443244] New: find next/previous icon inconsistence
https://bugs.kde.org/show_bug.cgi?id=443244 Bug ID: 443244 Summary: find next/previous icon inconsistence Product: konsole Version: 19.12.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: keyboard Assignee: konsole-de...@kde.org Reporter: emilyseville...@gmail.com Target Milestone: --- There is an inconsistence in find next/previous icons in terminal and shortcut settings. STEPS TO REPRODUCE OBSERVED RESULT In terminal find next is an arrow up and in shortcuts it is an arrow down, the same applies for find previous but contradictionary. EXPECTED RESULT Find next must be have an arrow down icon and find previous an arrow up icon in both places (terminal and shortcut settings). SOFTWARE/OS VERSIONS OS: Linux Mint 20.2 Cinnamon ADDITIONAL INFORMATION Konsole is installed via "sudo apt install konsole -y". -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443238] unable to connect to ubuntu 20.04 installed Mysql server 8.0.26
https://bugs.kde.org/show_bug.cgi?id=443238 Gerry Matte changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |WORKSFORME --- Comment #5 from Gerry Matte --- Well - I'm happy to report that my problem has been resolved and digiKam is now connecting to mysql with no problems. My final test was an attempt to instead use SQLite as the database but that failed because it reported that I had not yet installed SQLite. I had assummed it would be included in the appimage but no such luck. After completing this bug report I rebooted my pc and went for a soak in my hot tub. When I came back to the pc I tried running the appimage again and got the same error that SQLite was not installed. But since the database connection screen was right there I changed the database back to MySQL Server and set the rest of the parameters - when I used "Check Connection" it passed ! When it continued it completed some large downloads and started ok. After a restart of the appimage, digiKam then scanned my ~/Pictures folder successfully. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 441846] Tags duplicated with copy an event
https://bugs.kde.org/show_bug.cgi?id=441846 --- Comment #10 from Max --- Korganizer is my main planner app. With Manjaro updated up to KO 5.18.1 and kde-frameworks 5.86 the duplication appears on opening any events details dialog. The screenshots demonstrate changing of tag editor state after cold start and opening event dialog -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 384267] Found text (ctrl-f) highlight color should use System Settings "selection background" color, not be hard-coded yellow
https://bugs.kde.org/show_bug.cgi?id=384267 --- Comment #18 from Paul Preney --- I missed mentioning I am using Okular v21.08.1 --but all past versions also have these issues. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 384267] Found text (ctrl-f) highlight color should use System Settings "selection background" color, not be hard-coded yellow
https://bugs.kde.org/show_bug.cgi?id=384267 Paul Preney changed: What|Removed |Added CC||p...@preney.ca --- Comment #17 from Paul Preney --- I also have issues with this. I run with KDE Night Mode enabled (i.e., the screen is significantly shifted towards yellow/orange). This causes yellow highlights to become essentially invisible (or very hard to to see) on the page. Also I regularly search PDFs with lots of small text and it can be hard (even without Night Mode on) to easily find bright-yellow on the page. More contrast to improve visibility is needed with Ctrl-F highlighting. ASIDE: Yellow is a great highlight colour when NOT using Night Mode, colour inversion, large text, and/or reviewing using yellow --otherwise it is the worst (as implemented in okular since Night Mode renders it essentially invisible, inversion makes it unseen-black and viewing using yellow essentially makes it unseen if the two overlap). Choosing any of the Accessibility settings does not work since none of these changes the highlight to something noticeable/contrasting. In most situations those settings the Ctrl-F hard-coded yellow background becomes invisible (i.e., essentially black if inverting colours) and although the letters highlighted are a slightly brighter/bolder yellow but such is not easy to see with Night Mode off (and essentially impossible to see with it on). I would like to ask that the Ctrl-F highlight be configurable as follows: * Status quo: Default to what currently happens. * Allow the user under Accessibility to choose a some sort of "High contrast invert" for Ctrl-F matches. The high contrast invert would completely invert what is underneath the Ctrl-F highlight box. Sure if the area underneath is 50% gray the inversion would be ~50% gray, i.e., useless, but Ctrl-F matches text and virtually all PDF pages have significant contrast between text and what is underneath the text so that a colour inversion should be very visible. Most documents though, the inversion would make Ctrl-F finds white letter with a black background. It would also be ideal to make user-customizable the colour of the border of the box that surrounds the Ctrl-F yellow highlight. The current colour "black" is useless: it blends in to the page's text (i.e., it doesn't draw the user's attention to the found text) and if Accessibility's invert colour (etc.) is chosen it becomes invisible, etc. Currently there are times when the only way I can see where a match is on a page is to turn off Night Mode completely --and even then I have to look carefully because most PDFs I look at have a lot of small text in them --the yellow is too subtle a colour for such to stand out easily. -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 441846] Tags duplicated with copy an event
https://bugs.kde.org/show_bug.cgi?id=441846 --- Comment #9 from Max --- Created attachment 142109 --> https://bugs.kde.org/attachment.cgi?id=142109=edit Tag Editor state after open an event dialog Tag Editor state after open an event dialog -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 441846] Tags duplicated with copy an event
https://bugs.kde.org/show_bug.cgi?id=441846 --- Comment #8 from Max --- Created attachment 142108 --> https://bugs.kde.org/attachment.cgi?id=142108=edit Tag Editor state after cold start Tag Editor state after cold start -- You are receiving this mail because: You are watching all bug changes.
[korganizer] [Bug 441846] Tags duplicated with copy an event
https://bugs.kde.org/show_bug.cgi?id=441846 --- Comment #7 from Max --- Created attachment 142107 --> https://bugs.kde.org/attachment.cgi?id=142107=edit KO state after cold start KO state after cold start -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 443243] New: I am unable to use Mysql database as data source.
https://bugs.kde.org/show_bug.cgi?id=443243 Bug ID: 443243 Summary: I am unable to use Mysql database as data source. Product: kmymoney Version: 5.1.1 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: database Assignee: kmymoney-de...@kde.org Reporter: ganeshcser...@zoho.com Target Milestone: --- Created attachment 142106 --> https://bugs.kde.org/attachment.cgi?id=142106=edit Error message Kindly provide handy user guide to configure use mysql database in kmymoney application. I am facing issue in QMYSQL. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 443242] New: Add support for Unicode character composition to Kate and KWrite
https://bugs.kde.org/show_bug.cgi?id=443242 Bug ID: 443242 Summary: Add support for Unicode character composition to Kate and KWrite Product: kate Version: 21.08.0 Platform: Other OS: FreeBSD Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: kwrite-bugs-n...@kde.org Reporter: grahamper...@gmail.com Target Milestone: --- SUMMARY I'd like to use Kate, but it lacks support for the character composition keystrokes to which I became accustomed after switching from Mac OS X to FreeBSD-based systems. I assume that Kate for Linux also lacks support. STEPS TO REPRODUCE 1. Perform these six keystrokes: Control-Shift-U 2 0 2 6 Space bar OBSERVED RESULT 2026 ^ – there's a space EXPECTED RESULT … – a single character. SOFTWARE/OS VERSIONS % pkg query %v editors/kate 21.08.1 % uname -KU 1400033 1400033 % uname -a FreeBSD mowa219-gjp4-8570p-freebsd 14.0-CURRENT FreeBSD 14.0-CURRENT #109 main-n249408-ff33e5c83fa: Thu Sep 16 01:11:04 2021 root@mowa219-gjp4-8570p-freebsd:/usr/obj/usr/src/amd64.amd64/sys/GENERIC-NODEBUG amd64 % Operating System: FreeBSD 14.0 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 14.0-CURRENT (64-bit) Graphics Platform: X11 Memory: 15.9 GiB of RAM Graphics Processor: AMD TURKS ADDITIONAL INFORMATION Screenshots at https://github.com/psemiletov/tea-qt/issues/37 (for the same issue with TEA) should help to visualise this issue with Kate (and KWrite). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443241] New: menu cuts off content by 1 pixel
https://bugs.kde.org/show_bug.cgi?id=443241 Bug ID: 443241 Summary: menu cuts off content by 1 pixel Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: doncb...@gmail.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 142105 --> https://bugs.kde.org/attachment.cgi?id=142105=edit the highlight for Applications is cut off SUMMARY Kickoff appears to be one pixel lower than it needs to be. Tabbar that make use of it appear strange. STEPS TO REPRODUCE 1. Apply a theme whose tabbar svg has a thin line at the bottom for best visibility 2. Open Kickoff 3. OBSERVED RESULT The tabbar element for Applications and Places is cut off by 1 pixel at the bottom EXPECTED RESULT The entire tabbar element should be visible SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: 5.23.80 KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443240] New: separator looks strange when header and footer are absent from theme
https://bugs.kde.org/show_bug.cgi?id=443240 Bug ID: 443240 Summary: separator looks strange when header and footer are absent from theme Product: plasmashell Version: master Platform: Neon Packages OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: Application Launcher (Kickoff) Assignee: k...@davidedmundson.co.uk Reporter: doncb...@gmail.com CC: mikel5...@gmail.com, plasma-b...@kde.org Target Milestone: 1.0 Created attachment 142104 --> https://bugs.kde.org/attachment.cgi?id=142104=edit separator line now has large top and bottom space SUMMARY The separator in Kickoff has been changed to look continuous with the header and footer. However, when headers and footers are absent from a theme, the line is just awkwardly placed where it might normally connect, assuming that the header and footer style were wireframe like the line svg. STEPS TO REPRODUCE 1. Apply a theme without a plasmoidheading svg 2. Open Kickoff 3. OBSERVED RESULT Line is drawn separating the two panes with very large margins above and below it. EXPECTED RESULT Line should probably look similar to how it previously did and go from top to bottom. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION Upon writing this, the line may be problematic since it assumes that the theme has the wireframe appearance Breeze has instead of any other style. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436070] Unify lock screen and SDDM blur timeout
https://bugs.kde.org/show_bug.cgi?id=436070 --- Comment #3 from Nate Graham --- I know. But why do you think they need to be the same? -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 442675] [feature] - new indicators API in order to be able to be drawn more far to panel background roundness
https://bugs.kde.org/show_bug.cgi?id=442675 --- Comment #10 from doncb...@gmail.com --- (In reply to Michail Vourlakos from comment #9) > No worries, 0% corner margin means touching the farest edge of the > background roundness,so if you have big rounded background then 0% means out > of the background. Just to clarify question was if 0% would look more like No. 4 in this screenshot: https://bugs.kde.org/attachment.cgi?id=142041 Or if it looks like "1A" from https://bugs.kde.org/attachment.cgi?id=142084 >From what I understand, you are referring to the latter? -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 443239] Krusader crashes when attempting to view 7z file
https://bugs.kde.org/show_bug.cgi?id=443239 --- Comment #1 from Dan Dascalescu --- Created attachment 142103 --> https://bugs.kde.org/attachment.cgi?id=142103=edit File that causes the crash when viewed -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 443239] New: Krusader crashes when attempting to view 7z file
https://bugs.kde.org/show_bug.cgi?id=443239 Bug ID: 443239 Summary: Krusader crashes when attempting to view 7z file Product: krusader Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: krusader-bugs-n...@kde.org Reporter: ddascalescu+...@gmail.com CC: krusader-bugs-n...@kde.org Target Milestone: --- Application: krusader (2.7.2 "Peace of Mind") Qt Version: 5.15.3 Frameworks Version: 5.86.0 Operating System: Linux 5.4.0-84-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.5 Distribution: KDE neon User Edition 5.22 -- Information about the crash: Pressing F3 on perf.7z crashes the application. I'm writing this from the CRA, but don't yet see a way to upload that file. The crash can be reproduced every time. -- Backtrace: Application: Krusader (krusader), signal: Segmentation fault [New LWP 991694] [New LWP 991695] [New LWP 991696] [New LWP 991697] [New LWP 991698] [New LWP 991708] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7f5b8d977aff in __GI___poll (fds=0x7ffed124ac38, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7f5b8a36c9c0 (LWP 991692))] Thread 7 (Thread 0x7f5b72fa9700 (LWP 991708)): #0 0x7f5b8d977aff in __GI___poll (fds=0x7f5b58007170, nfds=3, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f5b780881d6 in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #2 0x7f5b78079841 in pa_mainloop_poll () from /lib/x86_64-linux-gnu/libpulse.so.0 #3 0x7f5b78079ec3 in pa_mainloop_iterate () from /lib/x86_64-linux-gnu/libpulse.so.0 #4 0x7f5b78079f70 in pa_mainloop_run () from /lib/x86_64-linux-gnu/libpulse.so.0 #5 0x7f5b7808811d in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0 #6 0x7f5b7336a72c in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-13.99.so #7 0x7f5b8d514609 in start_thread (arg=) at pthread_create.c:477 #8 0x7f5b8d984293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 6 (Thread 0x7f5b7a77a700 (LWP 991698)): #0 0x7f5b8d977aff in __GI___poll (fds=0x7f5b5c0143c0, nfds=1, timeout=-1) at ../sysdeps/unix/sysv/linux/poll.c:29 #1 0x7f5b8c60b36e in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x7f5b8c60b4a3 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7f5b8e0945eb in QEventDispatcherGlib::processEvents(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7f5b8e03887b in QEventLoop::exec(QFlags) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #5 0x7f5b8de52292 in QThread::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #6 0x7f5b8f206f4b in ?? () from /lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7f5b8de5342c in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7f5b8d514609 in start_thread (arg=) at pthread_create.c:477 #9 0x7f5b8d984293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 5 (Thread 0x7f5b7b107700 (LWP 991697)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f5b84008418) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f5b840083c8, cond=0x7f5b840083f0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f5b840083f0, mutex=0x7f5b840083c8) at pthread_cond_wait.c:638 #3 0x7f5b8247be7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f5b8247ba7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f5b8d514609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f5b8d984293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 4 (Thread 0x7f5b7b908700 (LWP 991696)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f5b84008418) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f5b840083c8, cond=0x7f5b840083f0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f5b840083f0, mutex=0x7f5b840083c8) at pthread_cond_wait.c:638 #3 0x7f5b8247be7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #4 0x7f5b8247ba7b in ?? () from /usr/lib/x86_64-linux-gnu/dri/iris_dri.so #5 0x7f5b8d514609 in start_thread (arg=) at pthread_create.c:477 #6 0x7f5b8d984293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 3 (Thread 0x7f5b7c109700 (LWP 991695)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x7f5b84008418) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x7f5b840083c8, cond=0x7f5b840083f0) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x7f5b840083f0, mutex=0x7f5b840083c8) at
[frameworks-plasma] [Bug 415601] Plasma tooltips draw shadows from the dialog svg instead of the tooltip svg
https://bugs.kde.org/show_bug.cgi?id=415601 --- Comment #4 from doncb...@gmail.com --- Created attachment 142102 --> https://bugs.kde.org/attachment.cgi?id=142102=edit different tooltip style using dialog's shadows -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 415601] Plasma tooltips draw shadows from the dialog svg instead of the tooltip svg
https://bugs.kde.org/show_bug.cgi?id=415601 doncb...@gmail.com changed: What|Removed |Added CC||doncb...@gmail.com Resolution|FIXED |--- Status|RESOLVED|REOPENED --- Comment #3 from doncb...@gmail.com --- (In reply to Nate Graham from comment #2) > Seems to be fixed now. How did you verify this and why is there no link to any changes? Reproduced on latest neon unstable 5.23.80. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443238] unable to connect to ubuntu 20.04 installed Mysql server 8.0.26
https://bugs.kde.org/show_bug.cgi?id=443238 --- Comment #4 from Gerry Matte --- Sorry for the extraneous boilerplate text "How to reproduce etc". I expected to be able to attach more than one file and I managed to do so but then could not see how to edit the original text. Gerry -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443238] unable to connect to ubuntu 20.04 installed Mysql server 8.0.26
https://bugs.kde.org/show_bug.cgi?id=443238 --- Comment #3 from Gerry Matte --- Created attachment 142101 --> https://bugs.kde.org/attachment.cgi?id=142101=edit digiKam database settings passed by Check Connections button -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 442504] Krusader opens no window with file transfer informations in KDE
https://bugs.kde.org/show_bug.cgi?id=442504 --- Comment #6 from Robert Strom --- Created attachment 142100 --> https://bugs.kde.org/attachment.cgi?id=142100=edit Example of the Salamander copy window minimized I would like the ability to minimize the copy window and get it out of the way while I continue working. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443238] unable to connect to ubuntu 20.04 installed Mysql server 8.0.26
https://bugs.kde.org/show_bug.cgi?id=443238 --- Comment #2 from Gerry Matte --- Created attachment 142099 --> https://bugs.kde.org/attachment.cgi?id=142099=edit mysql workbench connection to server and database tested ok -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 442504] Krusader opens no window with file transfer informations in KDE
https://bugs.kde.org/show_bug.cgi?id=442504 --- Comment #5 from Robert Strom --- Created attachment 142098 --> https://bugs.kde.org/attachment.cgi?id=142098=edit Altap Salamander copying file - copy windows has minimize button Note that the copy window has a minimize button. I have the ability to minimize the copy window and get it out of the way during a long copy (of which I have many of - multi-GB copies). I know that Krusader has the ability to minimize the copy window if I am using KUbuntu, but ther is no ability to minimize if I run Linux Mint Cinnamon, or Pop!_OS, and probably others. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443238] unable to connect to ubuntu 20.04 installed Mysql server 8.0.26
https://bugs.kde.org/show_bug.cgi?id=443238 --- Comment #1 from Gerry Matte --- Created attachment 142097 --> https://bugs.kde.org/attachment.cgi?id=142097=edit mysql workbench connected ok -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443238] New: unable to connect to ubuntu 20.04 installed Mysql server 8.0.26
https://bugs.kde.org/show_bug.cgi?id=443238 Bug ID: 443238 Summary: unable to connect to ubuntu 20.04 installed Mysql server 8.0.26 Product: digikam Version: 7.3.0 Platform: Appimage OS: Linux Status: REPORTED Severity: critical Priority: NOR Component: Database-Mysql Assignee: digikam-bugs-n...@kde.org Reporter: ge...@gerrymatte.ca Target Milestone: --- Created attachment 142096 --> https://bugs.kde.org/attachment.cgi?id=142096=edit mysql server status - server version etc I attempted to install using digiKam-7.3.0-x86-64.appimage on my ubuntu 20.04 system. While working through the initial setup wizard I encountered the database setup screen and discovered that I needed to setup a user and database in my mysql database server (see attachment mysql-workbench-server-status). I used the Mysql Workbench to create a user and database as shown in attachments mysql-workbench-pictures-connectionTest and mysql-workbench-picturesDB. After much trial and error with the mysql database workbench I eventually managed to successfully connect from the digiKam setup wizard and complete the remaining screens. The final accepted digiKam screen is attached as digikam-03. The wizard succeeded wnen I used it's "Check Connection" button. However, when I finished the setup it started connecting to my database and I received an error "Can't connect to local MySQL server through socket '/var/lib/mysql/mysql.sock' (13 "Permission denied") QMYSQL: Unable to connect". I decided to start over and simply use the SQLite database which I assumed would be included in the appimage file. However when I rerun the appimage file, it continues to attempt a connection to mysql. I would prefer to use my mysql server since I'm very familiar with it. But I am willing to change to using SQLite if that is the simplest option. If you are concerned that the digiKam "Check Connection" button accepted my database settings and then failed when scanning my Pictures folder I am willing to spend time attempting to work with you to determine the problem and resolve it. 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.
[krusader] [Bug 442504] Krusader opens no window with file transfer informations in KDE
https://bugs.kde.org/show_bug.cgi?id=442504 Robert Strom changed: What|Removed |Added CC||robert.st...@gmail.com --- Comment #4 from Robert Strom --- Created attachment 142095 --> https://bugs.kde.org/attachment.cgi?id=142095=edit Altap Salamander Starting Copy Example Picture of another dual pane file manager (this one running on Windows). I have used this file manager since the 1990's. Very, very similar to Krusader, also based on the "Norton Commander" style Dual Pane. This picture is just starting the copy (F5), just like you would in Krusader. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443237] New: focusing a window (with hover to focus) should not change its order on the "recently used" stack
https://bugs.kde.org/show_bug.cgi?id=443237 Bug ID: 443237 Summary: focusing a window (with hover to focus) should not change its order on the "recently used" stack Product: kwin Version: 5.22.4 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: kwin-bugs-n...@kde.org Reporter: adam.m.fontenot+...@gmail.com Target Milestone: --- SUMMARY This is a nit, but a major pain point for those using the "focus follows mouse" setting (in Settings > Window Management > Window Behavior > Window activation policy). When you briefly hover over an inactive window, but do not otherwise interact with it, KWin raises the window to the top of its *internal* stack of windows - it doesn't raise the window to the top of the visible windows *on the screen*, but it otherwise behaves as if it *had* done so. STEPS TO REPRODUCE 1. Set focus follows mouse (mouse precedence) as your window activation policy. Delay focus is 0ms, Focus stealing prevention is Medium. 2. Open three windows. One should be maximized (your browser works fine), two should be small windows some distance apart from each other, and both of these should be on top of the maximized window. 3. Click on one of the small windows to focus it. Move the cursor to the other window (*passing over the background window*) and click on the other window. 4. Press alt-tab (or whatever shortcut you have to activate the task switcher). OBSERVED RESULT The window that the task switcher tries to activate is the background window, even though you never interacted with it or tried to raise it. EXPECTED RESULT The other small window should be selected by the task switcher. This is a very common pattern. You have something like your browser running maximized, and meanwhile you're working with two windows (say, a terminal and a code editor), and you need to copy something from one of these windows and paste it in the other. You try to alt-tab back to the initial window, but unfortunately the brief moment when the background window was focused was enough for KWin to move it to the top of the stack. Important note: I'm aware that the task switcher has a "stacking order" option. This seemingly does the *opposite* of what I want. When I am in a window on the top of the visible stack, and I alt-tab to go back to the previous window I was using, "stacking order" starts me at the *bottom* of the stack and moves up from there! I think it's sensible to have this option for people who want it (after all, if you're not using hover to focus then if "stacking order" worked in top-down fashion then it would - I think - behave identically to "recently used"). So I think the most reasonable understanding of this problem is as a bug in hover to focus: a window should not be considered recently used just because it was focused: it should only be recently used if I interacted with it, e.g. raised it by clicking. SOFTWARE/OS VERSIONS Linux: Arch Linux x86_64 (kernel 5.14.5) KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 443048] Copy / Move progress bar always on top and unable to minimize
https://bugs.kde.org/show_bug.cgi?id=443048 --- Comment #4 from Robert Strom --- Created attachment 142094 --> https://bugs.kde.org/attachment.cgi?id=142094=edit Pop!_OS System Notification are for Krusader -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 443048] Copy / Move progress bar always on top and unable to minimize
https://bugs.kde.org/show_bug.cgi?id=443048 --- Comment #3 from Robert Strom --- Created attachment 142093 --> https://bugs.kde.org/attachment.cgi?id=142093=edit Krusader Main Window and Copy Window no Minimize button -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 443048] Copy / Move progress bar always on top and unable to minimize
https://bugs.kde.org/show_bug.cgi?id=443048 --- Comment #2 from Robert Strom --- No, I don't believe that it helps. I tried looking back at the attachment picture that I posted but it is not showing when I click on it. I am posting two more pictures. One picture of the Krusader window with the Copy Window over it. This should clearly show that the Copy Window has no Minimize button. I can move the window out of the way and still access Krusader and move around in the program while the copy or move is happening but I cannot minimize the window. The second screenshot shows the System / Notifications area for Krusader. I am not seeing what I believe you are referring to. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442544] Krita 5.0's Shift modifier to change brush size is not behaving as expected.
https://bugs.kde.org/show_bug.cgi?id=442544 Tyson Tan changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #2 from Tyson Tan --- The experience has improved recently. Now I don't get the same jumping between sizes that I found when I reported the bug. There must be some kind of bug at that time that cause the issue. I think we can close this bug now. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 443236] Widgets on Latte Dock doesn't lose focus normally (X11).
https://bugs.kde.org/show_bug.cgi?id=443236 Lemuel Simon changed: What|Removed |Added CC||lemuelsimo...@protonmail.co ||m -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 443236] Widgets on Latte Dock doesn't lose focus normally (X11).
https://bugs.kde.org/show_bug.cgi?id=443236 --- Comment #1 from Lemuel Simon --- Created attachment 142092 --> https://bugs.kde.org/attachment.cgi?id=142092=edit My Latte Dock configuration file. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 443236] New: Widgets on Latte Dock doesn't lose focus normally (X11).
https://bugs.kde.org/show_bug.cgi?id=443236 Bug ID: 443236 Summary: Widgets on Latte Dock doesn't lose focus normally (X11). Product: lattedock Version: 0.10.2 Platform: openSUSE RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: application Assignee: mvourla...@gmail.com Reporter: lemuelsimo...@protonmail.com Target Milestone: --- Created attachment 142091 --> https://bugs.kde.org/attachment.cgi?id=142091=edit Latte Dock widget and focus bugs. SUMMARY It's difficult to explain. Toggling widgets, like the Application Launcher (Kickoff) via the mouse, opens and closes the widget normally. However, Latte Dock doesn't return the focus to the active window (The window is dimmed (inactive) before I click on it again.) Oddly enough, window focus would be returned normally if I toggle the Application Launcher via a keyboard shortcut, like Superkey. The system tray widget, in particular, re-opens immediately after I toggle it off via the mouse. I cannot close it until I click a window or blank area on the screen. All items in the system tray share this bug, except for the Audio Widget and the Clipboard <-- Those two toggle-close normally via the mouse, but they don't return focus to the active window, just like the Application Menu or any other widget. Trying the widgets on the default Plasma panel don't have the toggle issues. It also returns focus to windows normally. I'm in a X11 session, with Plasma 5.22.90. STEPS TO REPRODUCE 1. Click on a widget on Latte Dock to toggle open. 2. Click on widget again to close it. 3. Observe that either the widget re-opens immediately (System Tray) on toggle-off, or Latte Dock doesn't return focus to active window on Widget close. OBSERVED RESULT The widget re-opens immediately (System Tray) on toggle-off, the user must click elsewhere to close it. Latte Dock doesn't return focus to active window on widget close. EXPECTED RESULT Focus is returned to the active window. System Tray can toggle-off normally via mouse click. SOFTWARE/OS VERSIONS Operating System: openSUSE Leap 15.3 KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Kernel Version: 5.3.18-57-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-3320M CPU @ 2.60GHz Memory: 7.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 4000 ADDITIONAL INFORMATION I have attached both my current layout config file and a video with the problem in question. I have not tried it in the Wayland Session (sans Gnome, Wayland is immature). I have disabled all Kwin tiling scripts to test this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 432172] [wayland] ksmserver-logout-greeter takes quarter of the screen
https://bugs.kde.org/show_bug.cgi?id=432172 Ilya Bizyaev changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Ilya Bizyaev --- I can no longer reproduce the issue. I can no longer log out from the Wayland session, either (it seems to just log me back in), but that's probably unrelated, so clothing this ticket. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434756] Sometimes it stopped updating
https://bugs.kde.org/show_bug.cgi?id=434756 --- Comment #19 from Dmitri Koulikoff --- (In reply to Dmitri Koulikoff from comment #18) > Created attachment 142088 [details] > Screen rendering problem > > This is very irritating. I have to restart KDE regularly I forgot to mention the video is of Firefox 92.0.1 (64-Bit) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443235] Feature request: option to disable visual indication of window grouping
https://bugs.kde.org/show_bug.cgi?id=443235 --- Comment #1 from Artem --- Created attachment 142090 --> https://bugs.kde.org/attachment.cgi?id=142090=edit what I would like to see -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443235] New: Feature request: option to disable visual indication of window grouping
https://bugs.kde.org/show_bug.cgi?id=443235 Bug ID: 443235 Summary: Feature request: option to disable visual indication of window grouping Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Task Manager and Icons-Only Task Manager Assignee: h...@kde.org Reporter: pankro...@list.ru CC: plasma-b...@kde.org Target Milestone: 1.0 Flags: Usability+, VisualDesign+ Created attachment 142089 --> https://bugs.kde.org/attachment.cgi?id=142089=edit group folder icon SUMMARY The visual indication of the grouping of windows is not very nice and not very informative. The + sign looks like something foreign. STEPS TO REPRODUCE 1. Use window grouping in the system OBSERVED RESULT The + sign looks uninformative. EXPECTED RESULT We need a function to turn off the visual display of the grouping of windows on the panel. Or reworking it into something convenient by default. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: ADDITIONAL INFORMATION It is these little things that make up the convenience of use. They are worth taking care of to fix them. I apologize for my English, if it seemed to you unsightly (google translate). -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 434756] Sometimes it stopped updating
https://bugs.kde.org/show_bug.cgi?id=434756 --- Comment #18 from Dmitri Koulikoff --- Created attachment 142088 --> https://bugs.kde.org/attachment.cgi?id=142088=edit Screen rendering problem This is very irritating. I have to restart KDE regularly -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 436534] Report behaves incorrectly after configuration change
https://bugs.kde.org/show_bug.cgi?id=436534 David Houlden changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #1 from David Houlden --- Unable to reproduce in 5.1.2 so marking as resolved. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443234] New: [wish]: Custom settings for "Night Color" controlled by automated "operation mode"
https://bugs.kde.org/show_bug.cgi?id=443234 Bug ID: 443234 Summary: [wish]: Custom settings for "Night Color" controlled by automated "operation mode" Product: systemsettings Version: unspecified Platform: Debian unstable OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_nightcolor Assignee: plasma-b...@kde.org Reporter: proj...@schiermeier-it.de CC: kwin-bugs-n...@kde.org Target Milestone: --- Night color has this three panels for settings: https://i.redd.it/j7c055ndb4zy.png So this idea: In the "Operation mode: Automatic" I want 1. bind the beginning of Night Color to e.g. "sunset begins" 2. bind the end of Night Color to e.g "sunrise ends" 3. set the "Transition duration" to one minute or so That's all. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 442544] Krita 5.0's Shift modifier to change brush size is not behaving as expected.
https://bugs.kde.org/show_bug.cgi?id=442544 tomtomtomreportin...@gmail.com changed: What|Removed |Added CC||tomtomtomreportingin@gmail. ||com --- Comment #1 from tomtomtomreportin...@gmail.com --- Hey Tyson, it's been a couple weeks since this report: Do you still feel the same way about this issue? This change may have been born out of a user suggestion, so there might be conflicting opinions on this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 417523] "More options..." button of vertical Panel is hidden if I also have an always visible horizontal Panel on bottom of the screen
https://bugs.kde.org/show_bug.cgi?id=417523 doncb...@gmail.com changed: What|Removed |Added CC||doncb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 375066] Improve usability / appearance for adjacent panels
https://bugs.kde.org/show_bug.cgi?id=375066 doncb...@gmail.com changed: What|Removed |Added CC||doncb...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 443233] New: Wallpaper GHNS blocks actions on desktop
https://bugs.kde.org/show_bug.cgi?id=443233 Bug ID: 443233 Summary: Wallpaper GHNS blocks actions on desktop Product: frameworks-knewstuff Version: 5.86.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ad...@leinir.dk Reporter: karlsson.gabr...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY Opening the wallpaper GHNS window locks everything on the desktop until it's closed again STEPS TO REPRODUCE 1. Open "Configure Desktop and Wallpaper..." 2. Click "Get New Wallpapers..." 3. Try to do anything on the desktop, e.g. open context menu, desktop icons, etc. OBSERVED RESULT You are unable to do anything with the desktop until GHNS is closed again EXPECTED RESULT You can still interact with the desktop SOFTWARE: OS: Neon Testing Edition KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION It affects the most when it is open on another virtual desktop, since you will not find the blocking window in the taskbar. The same happens with the wallpaper plugins GHNS window. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 443232] KClock should play the notification sound regardless if the user has muted notification sounds in System Settings > Audio
https://bugs.kde.org/show_bug.cgi?id=443232 61kyl...@anonaddy.me changed: What|Removed |Added Summary|KClock could play the |KClock should play the |notification sound |notification sound |regardless if the user has |regardless if the user has |muted notification sounds |muted notification sounds |in System Settings > Audio |in System Settings > Audio -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 443232] KClock could play the notification sound regardless if the user has muted notification sounds in System Settings > Audio
https://bugs.kde.org/show_bug.cgi?id=443232 61kyl...@anonaddy.me changed: What|Removed |Added Summary|KClock could have an|KClock could play the |independent notification|notification sound |system |regardless if the user has ||muted notification sounds ||in System Settings > Audio -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 443232] New: KClock could have an independent notification system
https://bugs.kde.org/show_bug.cgi?id=443232 Bug ID: 443232 Summary: KClock could have an independent notification system Product: frameworks-kirigami Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: notm...@gmail.com Reporter: 61kyl...@anonaddy.me Target Milestone: Not decided Currently, KClock notification system is tied up to Plasma. If the user muted the notification sounds in System Settings > Audio, the notification sounds of KClock won't play. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413165] Please add option to reduce screen brightness in kcm_nightcolor
https://bugs.kde.org/show_bug.cgi?id=413165 --- Comment #10 from Matija Kovačević --- (In reply to Matija Kovačević from comment #9) > The feature would be great! > > An addition to the following would be great: > When working in the setup with the closed laptop's lid and monitor, one > could use the try widget/icon for battery (To show Energy information), to > increase/decrease the brightness for the currently "active" monitor. > Or when the laptop lid is open, for all monitors, or some option to choose. TYPO FIXES: - use the tray widget/icon by scrolling the mouse-wheel - now it works only for my laptop screen, but not for the connected monitor -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 413165] Please add option to reduce screen brightness in kcm_nightcolor
https://bugs.kde.org/show_bug.cgi?id=413165 Matija Kovačević changed: What|Removed |Added CC||kdebugrep...@mailinator.com --- Comment #9 from Matija Kovačević --- The feature would be great! An addition to the following would be great: When working in the setup with the closed laptop's lid and monitor, one could use the try widget/icon for battery (To show Energy information), to increase/decrease the brightness for the currently "active" monitor. Or when the laptop lid is open, for all monitors, or some option to choose. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443228] Animated GIFs do not play in Presentation mode
https://bugs.kde.org/show_bug.cgi?id=443228 Maik Qualmann changed: What|Removed |Added Severity|normal |wishlist CC||metzping...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-knewstuff] [Bug 443231] New: Opening GHNS that is already open out of view doesn't bring it forward
https://bugs.kde.org/show_bug.cgi?id=443231 Bug ID: 443231 Summary: Opening GHNS that is already open out of view doesn't bring it forward Product: frameworks-knewstuff Version: 5.86.0 Platform: Other OS: Linux Status: REPORTED Severity: minor Priority: NOR Component: general Assignee: ad...@leinir.dk Reporter: karlsson.gabr...@gmail.com CC: kdelibs-b...@kde.org Target Milestone: --- Created attachment 142087 --> https://bugs.kde.org/attachment.cgi?id=142087=edit Video example SUMMARY If you try to open a GHNS window that is already open behind another window or minimized, it does not bring it forward into view STEPS TO REPRODUCE 1. Open "Add Widgets..." 2. Click "Get New Widgets..." and "Download New Plasma Widgets" 3. Click the GHNS window out of view (minimize or cover with another window) 4. Repeat the first two steps OBSERVED RESULT The GHNS window doesn't pop back into view EXPECTED RESULT The GHNS window reappears on top SOFTWARE OS: Neon Testing Edition KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.87.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443230] Sensors that report used/free percentage/space are not consistently updated when a file system is mounted/unmounted
https://bugs.kde.org/show_bug.cgi?id=443230 --- Comment #1 from Patrick Silva --- Created attachment 142086 --> https://bugs.kde.org/attachment.cgi?id=142086=edit 2nd video - re-mounting file systems after re-login -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443230] New: Sensors that report used/free percentage/space are not consistently updated when a file system is mounted/unmounted
https://bugs.kde.org/show_bug.cgi?id=443230 Bug ID: 443230 Summary: Sensors that report used/free percentage/space are not consistently updated when a file system is mounted/unmounted Product: plasmashell Version: 5.22.90 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: System Monitor Assignee: plasma-b...@kde.org Reporter: bugsefor...@gmx.com CC: ahiems...@heimr.nl, notm...@gmail.com Target Milestone: 1.0 Created attachment 142085 --> https://bugs.kde.org/attachment.cgi?id=142085=edit 1st video - unmounting file systems SUMMARY I use 3 internal hard disks with 5 partitions in total, all of them are mounted on boot. Please watch the attached screen recordings. In the first attached video I unmount 4 secondary partitions after boot, then all sensors of all file systems are still displaying the same values. I think this result is not expected. In the second video recorded after re-login, we can notice that all sensors of the widget titled "All Partitions" report updated values that do not take the file systems unmounted in the first video into account. All sensors of "All Partitions" widget are immediately updated after mounting each file system - expected behavior in my point of view. But all sensors from the other widgets (WD, SEAGATE, WIN7, 2TB) are still missing. They reappear after restarting plasma with 'plasmashell --replace". STEPS TO REPRODUCE 1. use a machine with secondary partition(s) that you can unmount while the system is used 2. add 'System monitor Sensor' widget to desktop 3. open widget settings and go to 'Sensors details' section 4. click on 'Sensors' or "Text-only sensors' rows 5. click on 'Disks' category and add sensors that report used/free percentage/space of your file systems 6. click on 'Ok' button 7. unmount and re-mount your file systems OBSERVED RESULT Sensors that report used/free percentage/space are not consistently updated when a file system is mounted/unmounted EXPECTED RESULT All sensors that report used/free percentage/space should be immediately updated when a file system is mounted/unmounted Operating System: Arch Linux KDE Plasma Version: 5.22.90 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 Graphics Platform: Wayland -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 442675] [feature] - new indicators API in order to be able to be drawn more far to panel background roundness
https://bugs.kde.org/show_bug.cgi?id=442675 --- Comment #9 from Michail Vourlakos --- (In reply to doncbugs from comment #7) > Created attachment 142084 [details] > margins and border padding No worries, 0% corner margin means touching the farest edge of the background roundness,so if you have big rounded background then 0% means out of the background. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 442675] [feature] - new indicators API in order to be able to be drawn more far to panel background roundness
https://bugs.kde.org/show_bug.cgi?id=442675 --- Comment #8 from Michail Vourlakos --- (In reply to doncbugs from comment #7) > Created attachment 142084 [details] > margins and border padding No worries, 0% corner margin means touching the farest edge of the background roundness,so if you have big rounded background then 0% means out of the background. -- You are receiving this mail because: You are watching all bug changes.
[KDE Itinerary] [Bug 443199] Feature Request: Integration with Öffi/Transportr
https://bugs.kde.org/show_bug.cgi?id=443199 --- Comment #4 from ci3...@gmail.com --- Done for Transportr (https://github.com/grote/Transportr/issues/787). Öffi has no bug tracker (or at least I did not found one). -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 443229] New: python highlights on f-string not work.
https://bugs.kde.org/show_bug.cgi?id=443229
Bug ID: 443229
Summary: python highlights on f-string not work.
Product: kate
Version: 21.08.1
Platform: Manjaro
OS: Linux
Status: REPORTED
Severity: minor
Priority: NOR
Component: scripting
Assignee: kwrite-bugs-n...@kde.org
Reporter: osniel...@gmail.com
Target Milestone: ---
python f-string syntax not working correctly, highlights "f" as an error.
STEPS TO REPRODUCE
todo = "text"
print(f"show {todo}")
Operating System: Manjaro Linux
KDE Plasma Version: 5.22.5
KDE Frameworks Version: 5.86.0
Qt Version: 5.15.2
Kernel Version: 5.13.19-2-MANJARO (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i3-7130U CPU @ 2.70GHz
Memory: 11.6 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 620
--
You are receiving this mail because:
You are watching all bug changes.
[digikam] [Bug 443228] Animated GIFs do not play in Presentation mode
https://bugs.kde.org/show_bug.cgi?id=443228 John Preston changed: What|Removed |Added CC||gizmog...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 443228] New: Animated GIFs do not play in Presentation mode
https://bugs.kde.org/show_bug.cgi?id=443228 Bug ID: 443228 Summary: Animated GIFs do not play in Presentation mode Product: digikam Version: 7.3.0 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Plugin-Generic-Presentation Assignee: digikam-bugs-n...@kde.org Reporter: gizmog...@gmail.com Target Milestone: --- SUMMARY Hello, When I start a presentation via View > Presentation... , any animated GIFs in the image selection do not play, instead only the first frame of the GIF is displayed. This is contrary to Slideshow mode, where animated GIFs do play. In Slideshow, an animated GIF will play for it's entire duration, regardless of the slideshow delay setting. So e.g. if I have a GIF that's 4 seconds long and my slideshow is set at 2 seconds interval, the GIF will still take up 4 seconds. I think Presentation mode should play animated GIFs and have an option to either play the GIF to completion, or play the GIF up to the presentation interval time, and then move on to the next image. This is consistent with how nomacs handles presentations/slideshows with animated GIFs. I am using digiKam 7.3.0. Thanks! STEPS TO REPRODUCE 1. Add some animated GIFs to your library 2. Start Presentation 3. Observe GIFs are not animated OBSERVED RESULT Animated GIFs in Presentation just show first frame. EXPECTED RESULT Animated GIFs in Presentation should be animated. SOFTWARE/OS VERSIONS Linux: 5.14.8 KDE Plasma Version: Unknown (using i3wm) KDE Frameworks Version: /unknown (using i3wm) Qt Version: Unknown (whatever digiKam 7.3.0 in Arch is built against) ADDITIONAL INFORMATION Not tested yet in 7.4.0 but I can give it a go. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 442675] [feature] - new indicators API in order to be able to be drawn more far to panel background roundness
https://bugs.kde.org/show_bug.cgi?id=442675 --- Comment #7 from doncb...@gmail.com --- Created attachment 142084 --> https://bugs.kde.org/attachment.cgi?id=142084=edit margins and border padding -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 442675] [feature] - new indicators API in order to be able to be drawn more far to panel background roundness
https://bugs.kde.org/show_bug.cgi?id=442675 --- Comment #6 from doncb...@gmail.com --- (In reply to Michail Vourlakos from comment #4) Upon further consideration, I believe a more traditional option may be present, but it would require drastic changes to how Latte currently allows configuration. I have added a screenshot to demonstrate this. The dark gray rectangle represents available space on the dock and the light gray rectangle represents the drawn dock. Green represents padding or 'thickness,' perhaps. With the new method there are "border margins" and "border padding." "A" shows small border margins, though I am unsure if zero should be the size of the items or be around 50% of their size. Essentially, "A" has all corners (at least) inside the dock's space. "B" shows 1x border margins and content is always inside, regardless of dock roundness. "C" shows "border padding" which adds space around the dock's rectangle. I see this as an extension of the Thickness control where it affects both the sides and the top and bottom. Or, it could have both top/bottom and left/right controls. What limitations do you see to this method over the present one? i.e. do you think this can support all current use cases, even if it might be less user-friendly? > My initial thoughts were to let all indicators to set two options: >a) Painted Area Thickness Margin (the painted area is considered centered > always so the thickness margin is used both for bottom and top margins) >b) Painted Area Roundness (the painted area is considered always a > centered rectangle but the indicator can specify the painted area roundness) > > Benefits: > - with [a+b] Latte could possibly define what is the best positioning of > panel background in order to feel right and it could also use some clipping > method > - [a+b] can be user-specified if that is what the indicator creator wants > at per dock/panel basis > - [a+b] could also be indicator auto-adjusted based on each indicators > settings and requirements > > On the other hand, the calculations for [a+b] could break in many ways so > this can not be a v0.10.x branch solution. I am not sure I follow this. Does it look anything like the diagram I uploaded? I cannot quite imagine where this would break. Unless the user was pursuing a style like in No. 4 of the previous screenshot. > What can be done at this point is to introduce in the Indicators API (at > v0.10.3 or v0.10.4) a new option probably called: "Corner Margin" that could > take values between 0 - 100% . Each Indicator will take the responsibility > to provide it or not for the user to alter. Latte and Plasma indicators > could possibly introduce it after the Indicators API has been extended by > default. That option default value will be 100% and that would mean the > current behavior, 50% would mean half distance from background edge and 0% > would mean almost touching it. This satisfies my use case. With respect to the proposal in the new screenshot, I say also consider negative ~25-50% as the minimum, like in the previous screenshot's No. 4. Something like allowing the end of a floating dock to be centered under an icon the edge of a list of tasks. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 436070] Unify lock screen and SDDM blur timeout
https://bugs.kde.org/show_bug.cgi?id=436070 medin changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from medin --- (In reply to Nate Graham from comment #1) > How come? What I meant by timeout is the time that lock or login screen takes to hide password field and other buttons and shows not blurred background image with only time and date. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 442659] GTK3 Window decoration assets generated by kde-gtk-config are now all blank with Breeze window decoration
https://bugs.kde.org/show_bug.cgi?id=442659 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #7 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/kde-gtk-config/-/merge_requests/37 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443227] New: The keyboard layout does not change through the tray using the mouse
https://bugs.kde.org/show_bug.cgi?id=443227 Bug ID: 443227 Summary: The keyboard layout does not change through the tray using the mouse Product: kwin Version: unspecified Platform: Fedora RPMs OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-x11-standalone Assignee: kwin-bugs-n...@kde.org Reporter: ko...@cyfra.ua Target Milestone: --- SUMMARY I am using 3 keyboard layouts (English, Ukrainian, Russian) and most of the time I am using two keyboard layouts (English and Ukrainian or English and Russian). To quickly change the keyboard layout I use the "Spare Layout" option (All Settings -> Input Devices -> Keyboard -> Layouts -> Spare Layouts). If I need to change a pair of keyboard layouts I using mouse and tray. Over the past few months, the keyboard layout with the mouse has not changed at all. The menu opens and responds to keys, but does not change the keyboard layout. STEPS TO REPRODUCE 1. Add more than two keyboard layouts 2. Turn on "Spare Layouts" and set "Main Layout count" to 2 3. Check "Spare Layouts" (Switching must be between two keyboard layouts) 4. Click right button of the mouse on the tray with languages 5. Select the spare language with the mouse and press the left button of the mouse 6. Check tray icon, must be with symbol/flag of new language 7. Now one of the languages will be replaced by a new one and again you can switch between the two keyboard layouts OBSERVED RESULT Language is not changing and icon too with the mouse EXPECTED RESULT Renewal of the ability to change the keyboard layout with the mouse and with the ability to change the backup layout SOFTWARE/OS VERSIONS Fedora release 34 (Thirty Four) KDE Plasma Version: 5.85.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION kwin-libs-5.22.5-1.fc34.x86_64 kwin-common-5.22.5-1.fc34.x86_64 kwin-x11-5.22.5-1.fc34.x86_64 kwin-wayland-5.22.5-1.fc34.x86_64 kwin-5.22.5-1.fc34.x86_64 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 419539] Krusader crashed while searching the text with the excepted folder
https://bugs.kde.org/show_bug.cgi?id=419539 Toni Asensi Esteve changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|VERIFIED|CLOSED --- Comment #20 from Toni Asensi Esteve --- Good, I tried the git version of Krusader (with other software which is more recent) and the problem wasn't seen. -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 442216] Saving a file edited in a remote directory
https://bugs.kde.org/show_bug.cgi?id=442216 Toni Asensi Esteve changed: What|Removed |Added CC||toni.ase...@kdemail.net --- Comment #4 from Toni Asensi Esteve --- Note: This is related to https://bugs.kde.org/show_bug.cgi?id=442217 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 442217] Edit a file in a remote directory with VSCode
https://bugs.kde.org/show_bug.cgi?id=442217 Toni Asensi Esteve changed: What|Removed |Added CC||toni.ase...@kdemail.net --- Comment #2 from Toni Asensi Esteve --- Note: This is related to https://bugs.kde.org/show_bug.cgi?id=442216 -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 441380] "Edit > Compare Folders" does nothing
https://bugs.kde.org/show_bug.cgi?id=441380 Toni Asensi Esteve changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[krusader] [Bug 443048] Copy / Move progress bar always on top and unable to minimize
https://bugs.kde.org/show_bug.cgi?id=443048 Toni Asensi Esteve changed: What|Removed |Added CC||toni.ase...@kdemail.net --- Comment #1 from Toni Asensi Esteve --- Davide Gianforte wrote about something related on https://bugs.kde.org/show_bug.cgi?id=442504 Is that information useful for you? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()
https://bugs.kde.org/show_bug.cgi?id=442990 --- Comment #11 from Matej Mrenica --- (In reply to Nate Graham from comment #10) > Since this bug report is about KWin crashing, let's get a new one for > plasmashell once this is fixed. It might also just be Bug 420160? Yes, it seems to be the same issue: ... Old primary output: QScreen(0x5646dd677450, name="HDMI-A-1") New primary output: QScreen(0x5646e12d8b70, name="") ... xdg_surface@44: error -1: invalid window geometry size (0x0) ... The Wayland connection experienced a fatal error: Protocol error -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()
https://bugs.kde.org/show_bug.cgi?id=442990 Nate Graham changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|ASSIGNED --- Comment #10 from Nate Graham --- Since this bug report is about KWin crashing, let's get a new one for plasmashell once this is fixed. It might also just be Bug 420160? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 443226] baloo_file Crashes With Extended Session
https://bugs.kde.org/show_bug.cgi?id=443226 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()
https://bugs.kde.org/show_bug.cgi?id=442990 --- Comment #9 from Matej Mrenica --- Your proposed change fixes this issue mostly. Session/kwin doesn't crash anymore and the internal screen is activated. But, plasmashell still crashes and there isn't a coredump generated. -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 440322] Connecting an external monitor but using laptop screen causes screen settings being to be reloaded in a loop
https://bugs.kde.org/show_bug.cgi?id=440322 --- Comment #3 from Matej Mrenica --- New log: https://pastebin.com/WWxRPUez #0 0x7f8eb31c4d22 in raise () at /usr/lib/libc.so.6 #1 0x7f8eb31ae90e in abort () at /usr/lib/libc.so.6 #2 0x7f8eb3ae2abe in () at /usr/lib/libQt5Core.so.5 #3 0x7f8eb3ae1dd0 in qt_assert_x(char const*, char const*, char const*, int) () at /usr/lib/libQt5Core.so.5 #4 0x7f8eade58d72 in KWin::EglGbmBackend::removeOutput(KWin::DrmAbstractOutput*) (this=0x5591dc154230, drmOutput= 0x5591dcb18d60) at /tmp/kwin/src/plugins/platforms/drm/egl_gbm_backend.cpp:213 #5 0x7f8eade4e681 in QtPrivate::FunctorCall, QtPrivate::List, void, void (KWin::AbstractEglDrmBackend::*)(KWin::DrmAbstractOutput*)>::call(void (KWin::AbstractEglDrmBackend::*)(KWin::DrmAbstractOutput*), KWin::AbstractEglDrmBackend*, void**) (f= table offset 224, o=0x5591dc154230, arg=0x7fffc8ab8000) at /usr/include/qt/QtCore/qobjectdefs_impl.h:152 #6 0x7f8eade4e525 in QtPrivate::FunctionPointer::call, void>(void (KWin::AbstractEglDrmBackend::*)(KWin::DrmAbstractOutput*), KWin::AbstractEglDrmBackend*, void**) (f= table offset 224, o=0x5591dc154230, arg=0x7fffc8ab8000) at /usr/include/qt/QtCore/qobjectdefs_impl.h:185 #7 0x7f8eade4e44b in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x5591dbf551d0, r=0x5591dc154230, a=0x7fffc8ab8000, ret=0x0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:418 #8 0x7f8eb3d4e39b in () at /usr/lib/libQt5Core.so.5 #9 0x7f8eade18030 in KWin::DrmGpu::outputDisabled(KWin::DrmAbstractOutput*) (this=0x5591dbfb0260, _t1=0x5591dcb18d60) at /tmp/kwin/build/src/plugins/platforms/drm/KWinWaylandDrmBackend_autogen/EWIEGA46WW/moc_drm_gpu.cpp:189 #10 0x7f8eade42803 in KWin::DrmGpu::removeOutput(KWin::DrmOutput*) (this=0x5591dbfb0260, output=0x5591dcb18d60) at /tmp/kwin/src/plugins/platforms/drm/drm_gpu.cpp:489 #11 0x7f8eade40b82 in KWin::DrmGpu::updateOutputs() (this=0x5591dbfb0260) at /tmp/kwin/src/plugins/platforms/drm/drm_gpu.cpp:198 #12 0x7f8eade1b2b2 in KWin::DrmBackend::updateOutputs() (this=0x5591dbf8ebe0) at /tmp/kwin/src/plugins/platforms/drm/drm_backend.cpp:350 #13 0x7f8eade1a86f in KWin::DrmBackend::handleUdevEvent() (this=0x5591dbf8ebe0) at /tmp/kwin/src/plugins/platforms/drm/drm_backend.cpp:270 #14 0x7f8eade2632a in QtPrivate::FunctorCall, QtPrivate::List<>, void, void (KWin::DrmBackend::*)()>::call(void (KWin::DrmBackend::*)(), KWin::DrmBackend*, void**) (f=(void (KWin::DrmBackend::*)(KWin::DrmBackend * const)) 0x7f8eade1a18e , o=0x5591dbf8ebe0, arg=0x7fffc8ab84d0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:152 #15 0x7f8eade25523 in QtPrivate::FunctionPointer::call, void>(void (KWin::DrmBackend::*)(), KWin::DrmBackend*, void**) (f=(void (KWin::DrmBackend::*)(KWin::DrmBackend * const)) 0x7f8eade1a18e , o=0x5591dbf8ebe0, arg=0x7fffc8ab84d0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:185 #16 0x7f8eade244e9 in QtPrivate::QSlotObject, void>::impl(int, QtPrivate::QSlotObjectBase*, QObject*, void**, bool*) (which=1, this_=0x5591dbfb2b00, r=0x5591dbf8ebe0, a=0x7fffc8ab84d0, ret=0x0) at /usr/include/qt/QtCore/qobjectdefs_impl.h:418 #17 0x7f8eb3d4e39b in () at /usr/lib/libQt5Core.so.5 #18 0x7f8eb3d518fe in QSocketNotifier::activated(QSocketDescriptor, QSocketNotifier::Type, QSocketNotifier::QPrivateSignal) () at /usr/lib/libQt5Core.so.5 #19 0x7f8eb3d5210d in QSocketNotifier::event(QEvent*) () at /usr/lib/libQt5Core.so.5 #20 0x7f8eb4b90772 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5 #21 0x7f8eb3d15aa8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5 #22 0x7f8eb3d6d654 in QEventDispatcherUNIXPrivate::activateSocketNotifiers() () at /usr/lib/libQt5Core.so.5 #23 0x7f8eb3d6dad5 in QEventDispatcherUNIX::processEvents(QFlags) () at /usr/lib/libQt5Core.so.5 #24 0x5591db04d4ae in QUnixEventDispatcherQPA::processEvents(QFlags) () #25 0x7f8eb3d1442c in QEventLoop::exec(QFlags) () at /usr/lib/libQt5Core.so.5 #26 0x7f8eb3d1cd24 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5 #27 0x5591dafbfb60 in main(int, char**) (argc=15, argv=0x7fffc8ab8c38) at /tmp/kwin/src/main_wayland.cpp:745 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 443226] New: baloo_file Crashes With Extended Session
https://bugs.kde.org/show_bug.cgi?id=443226 Bug ID: 443226 Summary: baloo_file Crashes With Extended Session Product: frameworks-baloo Version: 5.86.0 Platform: Ubuntu Packages OS: Linux Status: REPORTED Severity: crash Priority: NOR Component: Baloo File Daemon Assignee: baloo-bugs-n...@kde.org Reporter: ltstarwars...@gmail.com Target Milestone: --- Created attachment 142083 --> https://bugs.kde.org/attachment.cgi?id=142083=edit drkonqi crash report file SUMMARY baloo_file can crash during background operations during system idle time. STEPS TO REPRODUCE 1. Leave computer unattended for extended period of time (amount unknown) While it has happened before, it is rare and unpredictable, so cannot provide additional reproduction steps. OBSERVED RESULT baloo_file crashes. EXPECTED RESULT baloo_file continues operation. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Ubuntu 21.04 KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.86.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION Hardware: CPU: Ryzen 3950X GPU: AMD 5700 XT RAM: 32GB ECC 3200 MHz, JDEC default timings Motherboard: ASrock x570 Creator OS Drive: Corsair Force Series MP600 2TB NVMe Note, system is dual boot with Win10. baloo-kf5/hirsute,now 5.86.0-0ubuntu1~ubuntu21.04~ppa1 System is set up to get updates from the kbuntu updates and backports PPAs. Backtrace: Application: baloo_file (baloo_file), signal: Aborted [KCrash Handler] #4 __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:49 #5 0x7fc7801a1864 in __GI_abort () at abort.c:79 #6 0x7fc780204736 in __libc_message (action=action@entry=do_abort, fmt=fmt@entry=0x7fc780329b9c "%s\n") at ../sysdeps/posix/libc_fatal.c:155 #7 0x7fc78020d08c in malloc_printerr (str=str@entry=0x7fc78032c6d0 "malloc(): unaligned tcache chunk detected") at malloc.c:5628 #8 0x7fc78021242c in tcache_get (tc_idx=) at malloc.c:3103 #9 __GI___libc_malloc (bytes=512) at malloc.c:3221 #10 0x7fc7807a6e31 in QArrayData::allocate (objectSize=objectSize@entry=8, alignment=alignment@entry=8, capacity=capacity@entry=61, options=..., options@entry=...) at tools/qarraydata.cpp:218 #11 0x7fc780c35754 in QTypedArrayData::allocate (options=..., capacity=, capacity=, options=...) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qarraydata.h:224 #12 QVector::QVector (this=, asize=, this=, asize=) at /usr/include/x86_64-linux-gnu/qt5/QtCore/qvector.h:514 #13 0x7fc780c3bd16 in Baloo::IdTreeDB::get (this=this@entry=0x7ffc0d1d3570, docId=, docId@entry=95701560801166085) at ./src/engine/idtreedb.cpp:83 #14 0x7fc780c3da07 in Baloo::DocumentUrlDB::getId (fileName=..., docId=95701560801166085, this=0x7ffc0d1d35f0) at ./src/engine/documenturldb.cpp:214 #15 Baloo::DocumentUrlDB::getId (this=0x7ffc0d1d35f0, docId=95701560801166085, fileName=...) at ./src/engine/documenturldb.cpp:205 #16 0x7fc780c497d8 in Baloo::Transaction::documentId (this=this@entry=0x7ffc0d1d36a0, path=...) at ./src/engine/transaction.cpp:119 #17 0x5651ff5df635 in Baloo::MetadataMover::removeMetadata (this=this@entry=0x565200264360, tr=tr@entry=0x7ffc0d1d36a0, url=...) at ./src/file/metadatamover.cpp:60 #18 0x5651ff5df735 in Baloo::MetadataMover::removeFileMetadata (this=0x565200264360, file=...) at ./src/file/metadatamover.cpp:52 #19 0x7fc7809be5c7 in QtPrivate::QSlotObjectBase::call (a=0x7ffc0d1d3820, r=0x565200264360, this=0x5652002733e0) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #20 doActivate (sender=0x56520026fe70, signal_index=6, argv=argv@entry=0x7ffc0d1d3820) at kernel/qobject.cpp:3886 #21 0x7fc7809b7728 in QMetaObject::activate (sender=sender@entry=0x56520026fe70, m=, local_signal_index=local_signal_index@entry=3, argv=argv@entry=0x7ffc0d1d3820) at kernel/qobject.cpp:3946 #22 0x5651ff5dde22 in Baloo::PendingFileQueue::removeFileIndex (_t1=..., this=0x56520026fe70) at ./obj-x86_64-linux-gnu/src/file/baloofilecommon_autogen/EWIEGA46WW/moc_pendingfilequeue.cpp:228 #23 Baloo::PendingFileQueue::enqueue (this=0x56520026fe70, file=...) at ./src/file/pendingfilequeue.cpp:68 #24 0x5651ff5ddfe0 in Baloo::FileWatch::slotFileDeleted (this=0x7ffc0d1d4050, urlString=..., isDir=) at ./src/file/filewatch.cpp:105 #25 0x7fc7809be5c7 in QtPrivate::QSlotObjectBase::call (a=0x7ffc0d1d3a60, r=0x7ffc0d1d4050, this=0x565200273820) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:398 #26 doActivate (sender=0x565200273470, signal_index=8, argv=argv@entry=0x7ffc0d1d3a60) at kernel/qobject.cpp:3886 #27 0x7fc7809b7728 in QMetaObject::activate (sender=sender@entry=0x565200273470, m=, local_signal_index=local_signal_index@entry=5, argv=argv@entry=0x7ffc0d1d3a60) at kernel/qobject.cpp:3946 #28 0x5651ff5e7a75 in KInotify::deleted (_t2=false, _t1=..., this=0x565200273470) at
[konsole] [Bug 443212] Konsole resizes the window when switching virtual desktops when run outside KDE
https://bugs.kde.org/show_bug.cgi?id=443212 --- Comment #3 from Ahmad Samir --- No problem, it's a weird bug to describe :) -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 443212] Konsole resizes the window when switching virtual desktops when run outside KDE
https://bugs.kde.org/show_bug.cgi?id=443212 --- Comment #2 from gi1242 --- My apologies; I searched before posting, but somehow I didn't find Bug #441610. Thanks for fixing it. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 443225] New: Shortcuts with keynum keys are not usable with "Numeric keypad always enters digits" option.
https://bugs.kde.org/show_bug.cgi?id=443225 Bug ID: 443225 Summary: Shortcuts with keynum keys are not usable with "Numeric keypad always enters digits" option. Product: systemsettings Version: unspecified Platform: Gentoo Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: kcm_keys Assignee: plasma-b...@kde.org Reporter: ebray...@gmail.com CC: k...@david-redondo.de Target Milestone: --- SUMMARY Shortcuts with keynum keys are not usable with "Numeric keypad always enters digits (as in macOS)" option and the numkey lock disabled. STEPS TO REPRODUCE 1. Enable System Settings → Input Devices → Advanced → Compatibility options → Numeric keypad always enters digits (as in macOS) 2. Define a shortcut, for example: System Settings → Shortcuts → Kwin → Switch to Desktop 1: Meta+Num+1 OBSERVED RESULT If you press Meta+Num+1 with the numlock enabled all work fine, but if you disable numlock Meta+Num+1 will not work. When numlock is disabled xev show the correct key press events and also the correct key combinations are showed by the shortcut entries on the System Settings, but the actual shortcut action is not performed. EXPECTED RESULT Shortcut keyboard actions using a num keypad key should run regardless of the numlock state with the "Numeric keypad always enters digits (as in macOS)" option enabled. -- SOFTWARE/OS VERSIONS Operating System: Gentoo Linux KDE Plasma Version: 5.22.5 KDE Frameworks Version: 5.85.0 Qt Version: 5.15.2 Kernel Version: 5.10.61-gentoo (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i7 CPU 870 @ 2.93GHz Memory: 7.8 GiB of RAM Graphics Processor: AMD JUNIPER -- Regards -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()
https://bugs.kde.org/show_bug.cgi?id=442990 --- Comment #8 from Matej Mrenica --- (In reply to Zamundaaa from comment #7) > Yes it should, although KScreen should also already be turning the output on. > > If I interpret this correctly your setup is having the internal display > disabled, with the external one used? Is that also the situation where this > crash happens? Yes, that's correct, the crash happens when I disconnect an external monitor (Or when I reconnect it) if it's the only enabled screen. I did that just now and got the exact same output. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 443174] Plasmashell Crashes Upon Display Port Monitor Turning Off In Wayland
https://bugs.kde.org/show_bug.cgi?id=443174 ltstarwars...@gmail.com changed: What|Removed |Added Keywords||wayland -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 418605] Improve handling of network-based music collection
https://bugs.kde.org/show_bug.cgi?id=418605 Nate Graham changed: What|Removed |Added Status|RESOLVED|REPORTED Resolution|INTENTIONAL |--- --- Comment #5 from Nate Graham --- This bug isn't fixed yet just because you moved to another app. Re-opening. -- You are receiving this mail because: You are watching all bug changes.
[Elisa] [Bug 418605] Improve handling of network-based music collection
https://bugs.kde.org/show_bug.cgi?id=418605 Vladimir Yerilov changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #4 from Vladimir Yerilov --- Hi again. After disconnection from and re-connection to the NFS share where my collection resides, Elisa's unable to show any file due to removal (automatic removal I must say) of the source configured in its preferences. So I have to add that source back and wait for everything scanned/imported again. Sad. Well, I'm better off of this and return to Cantata. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 443151] Some fill pattern cannot be selected.
https://bugs.kde.org/show_bug.cgi?id=443151 var...@gmx.ch changed: What|Removed |Added CC||var...@gmx.ch --- Comment #12 from var...@gmx.ch --- I found a new bug maybe. But i looks like related to this bug and i wanna ad a comment first here. I tested it on the nigthly krita-nightly_96794d1.dmg on my macOS Big Sur. All patterns with the extension .pat aren’t showed correctly, they are just blank in the Library. But you have to undelete it first in the Resource Manager. And the Resource Manager doesn’t show it for local folders in addition, but in the local folders are all .pat patterns. Also in the Krita 4 and 3 default ressources. In summary: All .pat are blank (White) All .pat arent showed in the local folder in resource manager, also not as deleted, but in the beta1, they are shown normaly, also in the patter library. All .pat are marked as deleted in the Krita 4 default resources (same as beta1) All .pat aren't marked as deleted in Krita 3 default resources, but they are marked as deleted in the beta1. I hope this helps, if it is a new bug, then reply and i create a new bug report. -- You are receiving this mail because: You are watching all bug changes.
[plasma-systemmonitor] [Bug 443223] Use bit/s instead of Byte/s for data rates
https://bugs.kde.org/show_bug.cgi?id=443223 Paul Worrall changed: What|Removed |Added CC||p.r.worr...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 443224] New: Kwin puts header bar wrongly in some java apps
https://bugs.kde.org/show_bug.cgi?id=443224 Bug ID: 443224 Summary: Kwin puts header bar wrongly in some java apps Product: kwin Version: 5.22.4 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: platform-x11-nested Assignee: kwin-bugs-n...@kde.org Reporter: lucbo...@gmail.com Target Milestone: --- Usually when the application is loading there is a headerless window shown, but plasma wayland is not supressing the header bar in some java applications. So far I have encontered this problem with Eclipse and DBeaver. I had no problems with Itellij Idea. -- You are receiving this mail because: You are watching all bug changes.
[plasma-pa] [Bug 443220] Internal microphone not detected on startup
https://bugs.kde.org/show_bug.cgi?id=443220 Nicolas Fella changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |UPSTREAM CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- Please report this to https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 415933] Fonts of gtk3 apps installed via flatpak are not antialiased on Wayland
https://bugs.kde.org/show_bug.cgi?id=415933 Nate Graham changed: What|Removed |Added CC||n...@kde.org -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 443177] Cantor crashes when opening a new tab if all other tabs had been closed
https://bugs.kde.org/show_bug.cgi?id=443177 --- Comment #2 from Alexander Semke --- (In reply to tgnff242 from comment #0) > STEPS TO REPRODUCE > > 1. Start cantor. > 2. Close every open tab. > 3. Try to open a new tab-backend, or open a pre-existing file. Thanks for reporting this issue. It will be fixed in the next patch release. -- You are receiving this mail because: You are watching all bug changes.
[cantor] [Bug 443177] Cantor crashes when opening a new tab if all other tabs had been closed
https://bugs.kde.org/show_bug.cgi?id=443177 Alexander Semke changed: What|Removed |Added Version Fixed In||21.08.2 Status|CONFIRMED |RESOLVED Resolution|--- |FIXED Latest Commit||https://invent.kde.org/educ ||ation/cantor/commit/c79dd27 ||1010266e06523598c6993c55f32 ||eb0668 --- Comment #1 from Alexander Semke --- Git commit c79dd271010266e06523598c6993c55f32eb0668 by Alexander Semke. Committed on 02/10/2021 at 15:08. Pushed by asemke into branch 'release/21.08'. Don't crash when all worksheets were closed and a new one is created again. FIXED-IN: 21.08.2 M +5-0src/cantor.cpp https://invent.kde.org/education/cantor/commit/c79dd271010266e06523598c6993c55f32eb0668 -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 429774] Discover does not update the state of install or remove buttons after the action has been completed
https://bugs.kde.org/show_bug.cgi?id=429774 lucbo...@gmail.com changed: What|Removed |Added CC||lucbo...@gmail.com --- Comment #14 from lucbo...@gmail.com --- I tested using arch linux and fedora 34 kde, the behavior was the same as the one above -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()
https://bugs.kde.org/show_bug.cgi?id=442990 --- Comment #7 from Zamundaaa --- Yes it should, although KScreen should also already be turning the output on. If I interpret this correctly your setup is having the internal display disabled, with the external one used? Is that also the situation where this crash happens? -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 442990] Crash in KWin::Toplevel::setOutput()
https://bugs.kde.org/show_bug.cgi?id=442990 --- Comment #6 from Matej Mrenica --- Looking at the proposed changes, it looks like it would fix the issue of laptop screen not being turned on if an external monitor is unplugged? Because that's something I was considering reporting. -- You are receiving this mail because: You are watching all bug changes.
[ktimetracker] [Bug 442996] Update app icons in SVG in ktimetracker.git when https://bugs.kde.org/show_bug.cgi?id=442993 is fixed
https://bugs.kde.org/show_bug.cgi?id=442996 Alexander Potashev changed: What|Removed |Added Resolution|--- |FIXED Latest Commit||https://invent.kde.org/pim/ ||ktimetracker/commit/0cf98ac ||238cc1bdfdd127c08ae531a8ada ||e65bd0 Status|REPORTED|RESOLVED --- Comment #1 from Alexander Potashev --- Git commit 0cf98ac238cc1bdfdd127c08ae531a8adae65bd0 by Alexander Potashev. Committed on 02/10/2021 at 14:45. Pushed by aspotashev into branch 'master'. Import new icons from https://invent.kde.org/frameworks/breeze-icons. M +1-39 icons/breeze-dark/22-apps-ktimetracker.svg M +1-39 icons/breeze-dark/32-apps-ktimetracker.svg M +1-39 icons/breeze-dark/48-apps-ktimetracker.svg M +1-39 icons/breeze/22-apps-ktimetracker.svg M +1-39 icons/breeze/32-apps-ktimetracker.svg M +1-39 icons/breeze/48-apps-ktimetracker.svg https://invent.kde.org/pim/ktimetracker/commit/0cf98ac238cc1bdfdd127c08ae531a8adae65bd0 -- You are receiving this mail because: You are watching all bug changes.
