[kmymoney] [Bug 358410] Home page / account listing / several spaces in the account name are not displayed
https://bugs.kde.org/show_bug.cgi?id=358410 Thomas Baumgart changed: What|Removed |Added Resolution|WAITINGFORINFO |NOT A BUG Status|NEEDSINFO |RESOLVED -- You are receiving this mail because: You are watching all bug changes.
[gwenview] [Bug 439931] New: Menu entry "Start a slideshow" only on english
https://bugs.kde.org/show_bug.cgi?id=439931 Bug ID: 439931 Summary: Menu entry "Start a slideshow" only on english Product: gwenview Version: 21.04.3 Platform: Neon Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: gwenview-bugs-n...@kde.org Reporter: semen.voz...@gmail.com Target Milestone: --- SUMMARY Menu entry such as "Start a slideshow" and "Start a Slideshow with selected images" not shows on system lang (only on english) STEPS TO REPRODUCE 1. Set any system language exept english 2. Right click on folder contain images or several image files OBSERVED RESULT You'll see menu entry on english EXPECTED RESULT Menu entry on system language SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.3 -- You are receiving this mail because: You are watching all bug changes.
[kmenuedit] [Bug 438695] Application crashed upon removing keyboard shortcut
https://bugs.kde.org/show_bug.cgi?id=438695 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439862] cosmetic artifacts on canvas 5.0.0-prealpha (git c75e336)
https://bugs.kde.org/show_bug.cgi?id=439862 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #4 from Bug Janitor Service --- Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 438710] windows that have shadows look wrong when they spawn
https://bugs.kde.org/show_bug.cgi?id=438710 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 438692] Dolphin Crashes when attempting to download new services
https://bugs.kde.org/show_bug.cgi?id=438692 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 438602] Crash on opening system settings from plasma network applet
https://bugs.kde.org/show_bug.cgi?id=438602 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #4 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 438495] Latte Dock unfixable template errors
https://bugs.kde.org/show_bug.cgi?id=438495 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #3 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 438448] EVERY Login Discover-Notifier tells me to restart
https://bugs.kde.org/show_bug.cgi?id=438448 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 358410] Home page / account listing / several spaces in the account name are not displayed
https://bugs.kde.org/show_bug.cgi?id=358410 --- Comment #6 from Bug Janitor Service --- Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439899] A second fixed cursor in the center of the screen on top of all sometimes appears.
https://bugs.kde.org/show_bug.cgi?id=439899 --- Comment #1 from kostyarin --- Also, switching to waiting mode and back hides the frozen cursor. Seems, it's belongs to screen lock. Cursor just doesn't disappear entering system. -- You are receiving this mail because: You are watching all bug changes.
[kate] [Bug 436097] kate stops responding with big file
https://bugs.kde.org/show_bug.cgi?id=436097 Michal Humpula changed: What|Removed |Added CC||k...@hudrydum.cz Resolution|--- |FIXED Latest Commit||https://invent.kde.org/fram ||eworks/ktexteditor/-/commit ||/98424e067240fc6243434631ae ||2f95f5e9aca49e Status|REPORTED|RESOLVED --- Comment #2 from Michal Humpula --- Thanks for the report. I believe the observed slowdown was fixed in the latest ktexteditor. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 436675] File transfer from Windows to Android fails (it used to work earlier) (it works from Android to Windows)
https://bugs.kde.org/show_bug.cgi?id=436675 brute4s99 changed: What|Removed |Added CC||piyushaggarwal...@gmail.com --- Comment #2 from brute4s99 --- have you set any filesystem locations in the Share and Receive plugin yet? -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439930] clipboard usually unreadable
https://bugs.kde.org/show_bug.cgi?id=439930 David Chmelik changed: What|Removed |Added Platform|Other |Slackware Packages -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439930] New: clipboard usually unreadable
https://bugs.kde.org/show_bug.cgi?id=439930 Bug ID: 439930 Summary: clipboard usually unreadable Product: plasmashell Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Clipboard Assignee: plasma-b...@kde.org Reporter: dchme...@gmail.com Target Milestone: 1.0 SUMMARY The clipboard is usually unreadable, being medium-gray text on dark-gray background, even if you change to a light colour theme, in which case it should change back to black on white! STEPS TO REPRODUCE 1. Copy text. 2. Look at text in clipboard. 3. May not be able to read it. OBSERVED RESULT Can't read text unless you are very close to monitor (even with 20/20 vision.) EXPECTED RESULT There should be sufficiently contrasting text, like a traditional book page. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Slackware64-current KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 420939] Baloo purge not completing
https://bugs.kde.org/show_bug.cgi?id=420939 --- Comment #34 from Scott --- Created attachment 140106 --> https://bugs.kde.org/attachment.cgi?id=140106=edit mediainfo2 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 439929] New: Make XCursor-Viewer be part of KDE
https://bugs.kde.org/show_bug.cgi?id=439929 Bug ID: 439929 Summary: Make XCursor-Viewer be part of KDE Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: xenoida...@gmail.com Target Milestone: --- XCursor previews have been lost on Dolphin when it was ported to QT5 because of security problems. A great way to overcome this issue is by using XCursor-Viewer made by Ivan Romanov. The app is simple and very helpful to know how Cursor Theming is organized. I think it would be great if KDE forked a version of it, either as a KCM-Module, Dolphin Plug-In, or a stand alone app. Xcursor Github: https://github.com/drizt/xcursor-viewer -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 420939] Baloo purge not completing
https://bugs.kde.org/show_bug.cgi?id=420939 --- Comment #33 from Scott --- Created attachment 140105 --> https://bugs.kde.org/attachment.cgi?id=140105=edit mediainfo1 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 420939] Baloo purge not completing
https://bugs.kde.org/show_bug.cgi?id=420939 --- Comment #32 from Scott --- (In reply to Scott from comment #30) > ... just to confirm, what is the correct config setting/syntax to > enable content indexing: > 1/ Remove the line, only basic indexing=true, or, > 2/ Include the line, only basic indexing=false Yes. Or go through "System Settings > Search > File Search" and you'll see an "Also index file content" checkbox. - So here is the problem, the above information is not entirely correct. The settings in baloofilerc do not control whether full file indexing occurs. That control rests with the setting in System Settings > Search > File Search. Once that is enabled (ticked) the four files we spoke about yesterday are now more fully indexed and display valid data in the Duration column of Dolphin. It appears that the GUI takes precedent over the config file as including a directory in the config is ignored (not indexed) if that directory is selected as, Not indexed in the GUI. There are still issues with warning/error output: 1/ [mpegts @ 0x55e6d2be2d00] start time for stream 2 is not set in estimate_timings_from_pts 2/ [mpegts @ 0x55e6d2be2d00] Could not find codec parameters for stream 2 (Subtitle: hdmv_pgs_subtitle (pgssub) ([144][0][0][0] / 0x0090)): unspecified size 3/ Consider increasing the value for the 'analyzeduration' and 'probesize' options Is it possible to increase the values shown in item 3 above? Having had some success in having these 4 files indexed I proceeded to index a directory within the main disk array. Baloo was only able to index metadata on about 30% of the files. I then copied one indexed file and one not indexed file to the same directory as the previously mentioned 4 files and renamed them. I repeated the indexing and attempted single file indexing with the same result. I then deleted 2 of the video files, S01E04&5. My Test directory now has 4 files, 1 x mp3 file, 1 x initial video file, 1 new file with metadata not indexed and 1 new file with metadata indexed. Both new files are close to 15GB in size. As you are aware I have 2 terminal windows open during this process. When I unable balooctl the monitor window reports, Indexing: /directory.file.m2ts OK, for all 4 files. In the other terminal window error/warning messages are printed (the purple prefixed messages in my previous attachments) as shown in the numbered items above. The exception was the new file which did not have it's metadata indexed, where an additional error/warning message was displayed: [mpegts @ 0x5645497daec0] Failed to open codec in avformat_find_stream_info I then used a program, MediaInfo, to read the file details, which are attached and discovered that this file uses the VC-1 codec. This is a little surprising as this codec is quite an early one, dating back to 2006. I looked at several more files and found that the video codec is not the sole reason as I found numerous AVC that were not indexed and even for late model codecs such as H.265 some were indexed while others were not. -- You are receiving this mail because: You are watching all bug changes.
[Falkon] [Bug 439891] [Feature Request] Allow websites to detect dark or light theme in use
https://bugs.kde.org/show_bug.cgi?id=439891 Tony changed: What|Removed |Added CC||jodr...@live.com Summary|Allow websites to detect|[Feature Request] Allow |dark or light theme in use |websites to detect dark or ||light theme in use -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 438644] Dialog corners broken
https://bugs.kde.org/show_bug.cgi?id=438644 Matty R changed: What|Removed |Added CC|d...@rhoatech.com| -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439898] Unable to configure layout switch to Cpas Lock and disable Caps Lock mode on Shift+Caps Lock
https://bugs.kde.org/show_bug.cgi?id=439898 kostyarin changed: What|Removed |Added Ever confirmed|0 |1 Status|RESOLVED|REOPENED Resolution|INTENTIONAL |--- --- Comment #2 from kostyarin --- > I think it's not Plasma specific, > it's just default XKB configuration > files presented in distro. See > Advanced tab in KCM Keyboard Settings > for more options. > Did you see other behavior in other DEs? > You can make your own Caps Lock option > displayed in the KCM, by editing XKB files. > But that is out of scope here. It's completely Plasma bug. It doesn't called "Standard XKB configurations with funny pins". It's called keyboard configurations. Check it out https://imgur.com/xWIndhu Being a user, I expect this selection to work as it's expected. If it's called "Standard XKB configurations with funny pins" then no problems -- since no one know what it is and how it works. And a misbehavior is expected. But when I switch pins this way (see image), there is only one way how it should work. And it can't be seen in other DE. Jut to make it clear: - Have you ever hear about UX/UI? - What should got a user with such settings? - Is misleading one of KDE/Plasma goals? I think "It's standard XKB" is not the solution. --- P.S.: Also, looks like, all other DE misbehavior can be a reason to KDE misbehavior. "I just don't want to even delve into it" will be more fair. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439864] Dolphin resets to "Home" and forgets paths of all tabs that are not available on start [regression]
https://bugs.kde.org/show_bug.cgi?id=439864 Nate Graham changed: What|Removed |Added CC||n...@kde.org Resolution|--- |INTENTIONAL Status|REPORTED|RESOLVED --- Comment #1 from Nate Graham --- I'm afraid this is an intentional change; we had many complaints about Dolphin showing annoying "this path cannot be found" messages on launch when attempting to restore tabs for inaccessible locations. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439864] Dolphin resets to "Home" and forgets paths of all tabs that are not available on start [regression]
https://bugs.kde.org/show_bug.cgi?id=439864 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439903] System Tray does not respect Opaque panel setting for the panel it lives on
https://bugs.kde.org/show_bug.cgi?id=439903 Nate Graham changed: What|Removed |Added Summary|Opacity is not applied to |System Tray does not |Tray widgets and Widgets|respect Opaque panel |Adder |setting for the panel it ||lives on Status|REPORTED|CONFIRMED Component|Theme - Breeze |System Tray CC||mate...@gmail.com, ||n...@kde.org, ||niccolo.venera...@gmail.com Ever confirmed|0 |1 Assignee|visual-des...@kde.org |plasma-b...@kde.org --- Comment #1 from Nate Graham --- Seems like a bug; panel widgets other than the System Tray become opaque, but the System Tray does not. As for the Add Widgets sidebar, that's intentional because it's not connected to the panel itself. The Panel opacity setting is only supposed to concern the panel and any widgets on it. It's not a general "turn off all transparency in Plasma" button. -- You are receiving this mail because: You are watching all bug changes.
[Qt/KDE Flatpak Runtime] [Bug 436864] Grayscale antialiasing in apps using KDE Platform
https://bugs.kde.org/show_bug.cgi?id=436864 Ilya Fedin changed: What|Removed |Added CC||fedin-ilja2...@ya.ru --- Comment #4 from Ilya Fedin --- The issue you referring to is about metric-compatible fonts in runtime, not about font rendering settings passthrough. I don't think they can solve that, though, since fontconfig file format is incompatible between versions and host configs will refer to host directories. Looks like gtk uses XSETTINGS on X11 and portals on Wayland to get rendering settings via sandbox. I believe Qt QPA should be reorganized to get font rendering settings from platformtheme layer. That way, it will be able to get font rendering settings from gtk on gtk based DEs and from Plasma configs (via portals if running inside flatpak) on Plasma. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437919] System settings crashes everytime
https://bugs.kde.org/show_bug.cgi?id=437919 Nate Graham changed: What|Removed |Added Status|RESOLVED|CLOSED -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 437919] System settings crashes everytime
https://bugs.kde.org/show_bug.cgi?id=437919 Nate Graham changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REOPENED|RESOLVED --- Comment #4 from Nate Graham --- Using a newer version of the software. You are using version 5.12 which is over two years old. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439862] cosmetic artifacts on canvas 5.0.0-prealpha (git c75e336)
https://bugs.kde.org/show_bug.cgi?id=439862 --- Comment #3 from jojopay...@gmail.com --- I need to check. I kinda just picked that option because it's the only that said canvas. I'm not super programming savvy, sorry -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 439928] New: Spontaneous Latte Dock crash
https://bugs.kde.org/show_bug.cgi?id=439928 Bug ID: 439928 Summary: Spontaneous Latte Dock crash Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: skylake...@gmail.com Target Milestone: --- Application: latte-dock (0.10.75) Qt Version: 5.15.3 Frameworks Version: 5.84.0 Operating System: Linux 5.8.0-59-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.3 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: I was using the default KDE Plasma application menu, and then I made "right-click" to modify the icon of a program in the launcher, however, the dialog did not launch and instead Latte crashed. I've done this before and after without any problems, however, I make this bug report because KDE crash handler generated a backtrace that (in the program's own words) may be useful for the developer. My package was directly compiled from git (19defa08cd7f3fbeb403a028eced4d5751fa757b). The crash does not seem to be reproducible. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [New LWP 1484] [New LWP 1485] [New LWP 1486] [New LWP 1487] [New LWP 1488] [New LWP 1489] [New LWP 1492] [New LWP 1511] [New LWP 1512] [New LWP 1513] [New LWP 1514] [New LWP 1515] [New LWP 1516] [New LWP 1520] [New LWP 1535] [New LWP 1588] [New LWP 1933] [New LWP 1962] [New LWP 1984] [New LWP 2063] [New LWP 3195] [New LWP 3202] [New LWP 3203] [New LWP 3204] [New LWP 3205] [New LWP 3206] [New LWP 3207] [New LWP 3208] [New LWP 3209] [New LWP 3645] [New LWP 3646] [New LWP 3647] [New LWP 3648] [New LWP 3658] [New LWP 3659] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". 0x7feb500a6aff in __GI___poll (fds=0x7ffdf5f9bb38, nfds=1, timeout=1000) at ../sysdeps/unix/sysv/linux/poll.c:29 [Current thread is 1 (Thread 0x7feb4c5189c0 (LWP 1483))] Thread 36 (Thread 0x7fea677fe700 (LWP 3659)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564a5b943794) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564a5b943740, cond=0x564a5b943768) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564a5b943768, mutex=0x564a5b943740) at pthread_cond_wait.c:638 #3 0x7feb50589f2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7feb52763b44 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7feb52763fb9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7feb50583dbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7feb4f79b609 in start_thread (arg=) at pthread_create.c:477 #8 0x7feb500b3293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 35 (Thread 0x7fea67fff700 (LWP 3658)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564a63dd7784) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564a63dd7730, cond=0x564a63dd7758) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564a63dd7758, mutex=0x564a63dd7730) at pthread_cond_wait.c:638 #3 0x7feb50589f2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7feb52763b44 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7feb52763fb9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7feb50583dbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7feb4f79b609 in start_thread (arg=) at pthread_create.c:477 #8 0x7feb500b3293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 34 (Thread 0x7fea7d792700 (LWP 3648)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564a633046c0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x564a63304670, cond=0x564a63304698) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x564a63304698, mutex=0x564a63304670) at pthread_cond_wait.c:638 #3 0x7feb50589f2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7feb52763b44 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7feb52763fb9 in ?? () from /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7feb50583dbc in ?? () from /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7feb4f79b609 in start_thread (arg=) at pthread_create.c:477 #8 0x7feb500b3293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 33 (Thread 0x7fea7e053700 (LWP 3647)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x564a631d9a64) at
[neon] [Bug 417078] Unhelpful "Aborted due to failure" error message sometimes appears when updating Flatpak apps
https://bugs.kde.org/show_bug.cgi?id=417078 --- Comment #21 from Patrick Silva --- Thank you Jonathan. :) Now I'm able to install Chromium via Konsole, but Discover is still failing with "Aborted due to failure" message even after reboot. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 438644] Dialog corners broken
https://bugs.kde.org/show_bug.cgi?id=438644 Patrick Silva changed: What|Removed |Added CC||bugsefor...@gmx.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 438644] Dialog corners broken
https://bugs.kde.org/show_bug.cgi?id=438644 Patrick Silva changed: What|Removed |Added CC||ifs6n...@anonaddy.me --- Comment #11 from Patrick Silva --- *** Bug 439234 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439234] Border corners are not transparent in some areas like in system tray applets or in Kickoff
https://bugs.kde.org/show_bug.cgi?id=439234 --- Comment #3 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 438644 *** -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439750] small white area appears at the corners of PopUps
https://bugs.kde.org/show_bug.cgi?id=439750 Patrick Silva changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |DUPLICATE --- Comment #4 from Patrick Silva --- *** This bug has been marked as a duplicate of bug 438644 *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 438644] Dialog corners broken
https://bugs.kde.org/show_bug.cgi?id=438644 Patrick Silva changed: What|Removed |Added CC||sicher-mit-li...@mailbox.or ||g --- Comment #10 from Patrick Silva --- *** Bug 439750 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416633] Middle-click+drag to scroll
https://bugs.kde.org/show_bug.cgi?id=416633 --- Comment #3 from Xeno Idaltu --- 2) The second issue is speed. I feel that Firefox has become faster when scrolling. I don't know how to edit this issue yet. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 416633] Middle-click+drag to scroll
https://bugs.kde.org/show_bug.cgi?id=416633 --- Comment #2 from Xeno Idaltu --- Thank you Aldrin. I like the way I navigate on Dolphin now, however there are two issues. 1) Firefox, Falkon, Chromium, etc have now lost the "image/icon" that shows up under our cursor when we press/hold the middle button. I think we should edit Breeze Cursor themes to make the "all-scroll" image/icon show up instead. The tricky part is what name/numbers to use. Years ago, I saw a GitHub page with all possible names/numbers to use but currently don't have enough time to search around the web. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-plasma] [Bug 439847] Breeze SVGs used for third-party themes even though they shouldn't be
https://bugs.kde.org/show_bug.cgi?id=439847 Aleix Pol changed: What|Removed |Added Latest Commit||https://invent.kde.org/fram ||eworks/plasma-framework/com ||mit/f7d63bc30b2adbf420163d8 ||a8825e1ee9e125498 Resolution|--- |FIXED Status|REPORTED|RESOLVED --- Comment #2 from Aleix Pol --- Git commit f7d63bc30b2adbf420163d8a8825e1ee9e125498 by Aleix Pol Gonzalez, on behalf of Aleix Pol. Committed on 16/07/2021 at 00:47. Pushed by apol into branch 'master'. Theme::currentThemeHasImage should not return true if parent themes match M +5-1src/plasma/theme.cpp https://invent.kde.org/frameworks/plasma-framework/commit/f7d63bc30b2adbf420163d8a8825e1ee9e125498 -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 439927] Breeze Cursor Themes won't use "all-scroll" icon when pressing middle button of a mouse
https://bugs.kde.org/show_bug.cgi?id=439927 Xeno Idaltu changed: What|Removed |Added Summary|Breeze Cursor Themes won't |Breeze Cursor Themes won't |use Scroll icon when|use "all-scroll" icon when |pressed |pressing middle button of a ||mouse -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 439927] Breeze Cursor Themes won't use Scroll icon when pressed
https://bugs.kde.org/show_bug.cgi?id=439927 Xeno Idaltu changed: What|Removed |Added Summary|Breeze Cursor won't use |Breeze Cursor Themes won't |Scroll icon when pressed|use Scroll icon when ||pressed -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 439927] Breeze Cursor won't use Scroll icon when pressed
https://bugs.kde.org/show_bug.cgi?id=439927 Xeno Idaltu changed: What|Removed |Added CC||xenoida...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 439927] New: Breeze Cursor won't use Scroll icon when pressed
https://bugs.kde.org/show_bug.cgi?id=439927 Bug ID: 439927 Summary: Breeze Cursor won't use Scroll icon when pressed Product: Breeze Version: unspecified Platform: Debian stable OS: Linux Status: REPORTED Severity: task Priority: NOR Component: Icons Assignee: visual-des...@kde.org Reporter: xenoida...@gmail.com CC: kain...@gmail.com Target Milestone: --- On Firefox we enable Smooth Scroll. We press the middle button of our mouse, a circular icon shows up letting us know we can now scroll around. - Dolphin File Manager lacks this feature so I made a Xorg Configuration. 1) First I installed Xinput from Debian repos 2) I created file: /etc/X11/xorg.conf.d/40-libinput.conf 3) Inside the file I used this: Section "InputClass" Identifier "libinput pointer catchall" MatchIsPointer "on" MatchDevicePath "/dev/input/event*" Option "ScrollMethod" "button" Driver "libinput" EndSection = Everything works with the exception of the icon that shows up everytime we press the middle button. This icon no longer shows up on Firefox, Chromium, Falkon, etc. This has led me to believe that we must configure the Breeze Cursor Theme. Plasma's Breeze Cursor theme has an icon labeled "all-scroll" that should show up when pressing the middle button, maybe we need to use another word or a set of numbers. I theorize this because I've seen this behavior with Oxygen Cursor Themes where "size_bdiag" and "size_fdiag" revert back to Plasma's default Breeze Cursor "size_bdiag" and "size_fdiag". This happens because Oxygen Cursor Themes were made for KDE4 and lack certain name tagging. This is fixed by adding "ne_resize", "sw_resize", "nw_resize", "se_resize" to "size_bdiag" and "size_fdiag". Years ago when I was learning about this issue I came accross a Github page that had all possible names/numbers of Xcursor themes. Dolphin on KDE5 lacks Xcursor previews. Xcursor-Viewer needs to be installed to view Cursor themes. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439926] New: Virtual keyboard icon should become visible when user enters tablet mode by default
https://bugs.kde.org/show_bug.cgi?id=439926 Bug ID: 439926 Summary: Virtual keyboard icon should become visible when user enters tablet mode by default Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 At first it is rather confusing how to make the virtual keyboard open after installing it and enabling it in the KCM. That is so because it's hidden in the system tray among many other items by default. The user needs to pay particular attention when opening the tray to notice there is an additional tray icon for virtual keyboards, or already know it's there. It is not particularly discoverable. IMO the virtual keyboard icon should either be always visible once a virtual keyboard is found or be set to be visible once the user enters tablet mode. This makes the icon discoverable and easy to touch/toggle, and might even additionally serve as a tablet mode indicator. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 439925] New: Global touchscreen gestures
https://bugs.kde.org/show_bug.cgi?id=439925 Bug ID: 439925 Summary: Global touchscreen gestures Product: kwin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- The wayland session of GNOME 40 got a major uplift to touch gestures compared to GNOME 3.38. Here's a brief chat I had with Zamundaa mentioning this: https://www.reddit.com/r/kde/comments/oe2t8k/multitouch_touchscreen_gesture_support_in_kde/h449ahm?utm_source=share_medium=web2x=3 The changes to GNOME 40 were: * Drag window with one finger to corner : window snapping * Swipe to upper left corner : toggle overview * Swipe from the upper edge down on an empty space in the panel : get control and drag current window without using titlebar or headerbar * Swipe from the upper edge down on top of a top panel widget (like calendar, tray or a11y): open widget even if they're not visible (e.g. with zoom) * Swipe 3 or more fingers left or right : switch virtual desktops * Swipe 3 or more fingers up : open virtual desktops activities overview * Swipe 3 or more fingers left or right while in overview : switch virtual desktops * Swipe up again : open app drawer * Swipe 1 or more fingers while on app drawer : switch pages * Swipe app in virtual desktop thumbnail : pull it to different virtual desktop In other words, it was an amazing release for touchscreen support, and it fits their desktop well. As can be seen here, Plasma is already able to detect at least ten different fingers (even if it starts lagging at that point), as shown by the Touch Points desktop effect: https://www.reddit.com/r/kde/comments/od9bu6/unique_desktop_effect_for_touch_screens_touch/ Yet there's practically no touchscreen gestures. There was no report to track this either. Having touchscreen gestures at some point in the future would improve the Plasma experience IMO. This would also require quite some thought put into it, because global Plasma touchscreen gestures should: 1. Take into account the uniqueness of Plasma (it isn't one-axis-workspace centered like GNOME) 2. Take into account Plasma mobile (like Zamundaa mentions above) 3. Not break applications that also use touch input (Gwenview, Koko and Pix all have pinch to zoom for instance) Using 3 or more fingers like GNOME did looks like a good idea. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 --- Comment #62 from Sam Edwards --- I have just spent the past half-hour restarting powerdevil and plasmashell, including giving each one a head-start ranging from a few ms to a few hundred ms. The battery applet appeared every single time without fail. I can't make the issue occur in an *existing* session, only if I restart the entire desktop session does it (have a chance to) happen. Some third component must be involved at some level, so I tried adding kded5 to the mix for a few attempts to no avail. I'll keep trying to find the relevant process(es) between which this race is happening. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439924] New: The arrow shouldn't be needed to switch between categories using touch
https://bugs.kde.org/show_bug.cgi?id=439924 Bug ID: 439924 Summary: The arrow shouldn't be needed to switch between categories using touch Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- When using touch and System Settings is small enough as to merge the category panes (e.g. the one where Workspace behavior lies and the one where General behavior lies), one touch on top of the button to switch between panes isn't enough for the action to complete; you need to touch the arrow to return. This works if you advance, though. The only other way you can switch between panes is by swiping, but that's not intuitive at all, so it shouldn't be the default experience. It's a bit confusing, so let me exemplify: System Settings window is as small as can be, so both panes are merged. First pane contains things like Appearance, Workspace behavior, Window management, Shortcuts, Startup and shutdown, Search, etc. Second pane in Search contains things like File search, KRunner, Web search keywords. - You're on the first pane and you touch anywhere in the Search button except the arrow, it advances to the second pane. - You're on the first pane and you touch the arrow in the Search button, it advances to the second pane. - You're on the second pane and you touch anywhere in the Search button except the arrow, it DOES NOT return to the first pane. < This is the bug - You're on the second pane and you touch the arrow in the Search button, it returns to the first pane. While swiping works and it serves as a workaround for this issue, being unable to return to the previous pane by pressing anywhere in the button is still an inconsistency bug. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439909] Searching in current directory doesn't work alt all
https://bugs.kde.org/show_bug.cgi?id=439909 --- Comment #6 from Piotr Mierzwinski --- Created attachment 140104 --> https://bugs.kde.org/attachment.cgi?id=140104=edit file-search_settings-2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439909] Searching in current directory doesn't work alt all
https://bugs.kde.org/show_bug.cgi?id=439909 Piotr Mierzwinski changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|NOT A BUG |--- --- Comment #5 from Piotr Mierzwinski --- (In reply to tagwerk19 from comment #4) > (In reply to Piotr Mierzwinski from comment #0) > > Created attachment 140099 [details] > This says > Status: Not Running, 0% complete > > If baloo was stopped it would not notice and index files you've just added. > It could be you are seeing Bug 436352, where the indexer is paused but the > button still says "Pause Indexer". > > You can try a "balooctl status" from the command line to see what it thinks > the state of the indexer is or press the "Pause Indexer" button. Ups. I didn't notice that status was "Not running, 0% complete" Maybe I met Bug 436352, but in File Search I clicked nothing. I met status like on first screen shot just after I wanted to check file search status. Notice that when I click into button "Pause Indexer" then happens nothing - no any message changes in "File Search" window. It looks like on screen shot: "file-search_settings-2.png". Anyway I went to command line and called following commands: $ balooctl enable Enabling and starting the File Indexer .. and after couple seconds this one: $ balooctl status Baloo File Indexer is not running Total files indexed: 50,045 Files waiting for content indexing: 1 Files failed to index: 10 Current size of index is 345.79 MiB In attachment please find screenshot of search setting with strange message looking like a bug. Seems baloo failed (maybe because of broken links what I have in home directory), and stopped indexing before has found my newly created file. And info in GUI was: Status: Not running, 99% complete Currently indexing !% (I18N_ARGUMENT_MISSING) After restart of System Settings window, and checking "File Search" I found the same like on first screen shot. I wanted to know which files failed (cannot be indexed:), so I called: $ balooctl failed The following files could not be indexed: $ balooctl status [the same like above] Hmm. As you can see, is missing information I requested by command. Of course still I cannot find my file. Notice that ~/Documents is not symlink only regular folder. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439923] New: Headerbars containing module names in QML settings are hidden after swipe with touch
https://bugs.kde.org/show_bug.cgi?id=439923 Bug ID: 439923 Summary: Headerbars containing module names in QML settings are hidden after swipe with touch Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- SUMMARY This is actually a really widespread issue in Plasma, but I don't really know which product/component to report this to, and System Settings is the best example of this bug. My guess is it's something in frameworks. Swiping upwards in any QML settings module hides the headerbar containing the name of the module. By swiping upwards I mean a finger motion that begins from below and goes upwards, that is, it scrolls down. IMO this should not happen: 1. It does not fit the headerbars (containing the names of categories, like Appearance) to its left. 2. This behavior does not occur with the left headerbars when doing the same thing. 3. This is inconsistent with other KCMs that do not do the same thing even though they're also QML based. These are the KCMs that suffer from this issue: Global theme, Application Style, Plasma Style, Colors, Fonts, Icons, Cursors, Configure application launch feedback, Splash screen, General behavior, Screen locking, Login screen, Desktop session, File Search, Notifications, Accessibility, Default applications, Virtual keyboard, Display configuration, Night color. This also occurs in any settings that spawn in a different window, like those of the tray icons for audio and clipboard. And here are the KCMs that do not suffer from this issue: Window decorations**, Desktop effects*, Virtual desktops*, Activities*, Shortcuts*, Background services*, Users, Mouse**, Touchpad**, Audio. * = these don't seem to be QML or their entire content isn't scrollable(?) ** = these work exactly as expected STEPS TO REPRODUCE 1. Open any of the aforementioned KCMs: 2. Swipe upwards OBSERVED RESULT Headerbar gets hidden EXPECTED RESULT Headerbar doesn't change -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 439853] KAlarm crashes when launching
https://bugs.kde.org/show_bug.cgi?id=439853 David Jarvie changed: What|Removed |Added Status|REPORTED|RESOLVED Latest Commit||a063257b4bb673f3ab7d85a15a1 ||c926f9c768696 Resolution|--- |FIXED Version Fixed In||21.08.0 --- Comment #1 from David Jarvie --- This crash only occurs when using Wayland, when using multiple monitors. The code concerned checks whether an alarm window should be displayed on top of a full screen window: this code is for now disabled on Wayland. It is now fixed by commit a063257b4bb673f3ab7d85a15a1c926f9c768696, and will be in KAlarm version 3.3.0, which will be included in KDE apps release 21.08. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439922] New: Status and Notifications widget should optionally have wider arrow icon for increased touch surface
https://bugs.kde.org/show_bug.cgi?id=439922 Bug ID: 439922 Summary: Status and Notifications widget should optionally have wider arrow icon for increased touch surface Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: System Tray Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com CC: mate...@gmail.com Target Milestone: 1.0 In the tray, the arrow that opens up the Status and Notifications area containing hidden tray icons is really tiny, even when tray icons are scaled to a panel 70px tall. It's rather annoying to open considering that at such a panel size (and additionally a scale of 125% which I use) the other icons are really easy to touch accurately. It would be nice if said arrow would have the same width as the other visible tray icons that belong to the tray (the ones usually to its left). In order not to sacrifice space/compactness for general desktop users, perhaps just having the option to set a wider icon (or make it scale together with the other icons) would be ideal for touchscreens IMO. Something like: Panel icon: [ ] Small [X] Scale with Panel height [X] Including hidden icons arrow -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 --- Comment #61 from Sam Edwards --- Created attachment 140103 --> https://bugs.kde.org/attachment.cgi?id=140103=edit org.kde.powerdevil debug log when battery applet DOES appear As requested, here are the logs. Nothing stands out to me as an obvious culprit, but maybe the (power)devil's in the details. I was able to reproduce this issue without rebooting (I was starting the session from the terminal and using "log off" each time). It seemed to happen with a 90% rate under these circumstances. My upowerd PID was not changing between sessions, so we can rule out a race against upowerd's startup. (Yes, my laptop is on battery power; detecting no AC power is expected.) I'll next try restarting only powerdevil a few dozen times, unless a better diagnostic is proposed here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439921] New: Often widgets can't be moved with touch
https://bugs.kde.org/show_bug.cgi?id=439921 Bug ID: 439921 Summary: Often widgets can't be moved with touch Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: herzensch...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 In many instances, attempting to select a widget by press-and-hold with the finger does not always work, but that's a different issue. When it works, many times it is not possible to move the widget. This seems to only occur after it has been resized at least once, but that might be coincidental. This seems to work correctly more often when Edit mode is active, but from what I gather it should always work. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 --- Comment #60 from Sam Edwards --- Created attachment 140102 --> https://bugs.kde.org/attachment.cgi?id=140102=edit org.kde.powerdevil debug log when battery applet does NOT appear -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439898] Unable to configure layout switch to Cpas Lock and disable Caps Lock mode on Shift+Caps Lock
https://bugs.kde.org/show_bug.cgi?id=439898 Andrey changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |INTENTIONAL --- Comment #1 from Andrey --- I think it's not Plasma specific, it's just default XKB configuration files presented in distro. See Advanced tab in KCM Keyboard Settings for more options. Did you see other behavior in other DEs? You can make your own Caps Lock option displayed in the KCM, by editing XKB files. But that is out of scope here. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439920] New: Impossible to add widgets to the desktop by dragging via touch
https://bugs.kde.org/show_bug.cgi?id=439920 Bug ID: 439920 Summary: Impossible to add widgets to the desktop by dragging via touch Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Widget Explorer Assignee: plasma-b...@kde.org Reporter: herzensch...@gmail.com Target Milestone: 1.0 It is possible to add widgets to the desktop when using touch by double tapping a widget, which adds the widget to the upper left corner; this behavior is the same with mouse/touchpad and double clicking. Unlike the mouse, it's not possible to drag a widget from the widget explorer to the desktop with touch. The only way to add widgets to the desktop with a touchscreen is to double tap, enter edit mode and move it around to where you want it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439919] New: kio_http_cache_cleaner is not terminated after the main application is finished
https://bugs.kde.org/show_bug.cgi?id=439919 Bug ID: 439919 Summary: kio_http_cache_cleaner is not terminated after the main application is finished Product: frameworks-kio Version: 5.84.0 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: HTTP Assignee: kio-bugs-n...@kde.org Reporter: ralf.habac...@freenet.de CC: kdelibs-b...@kde.org Target Milestone: --- SUMMARY After working for some time with http kioslaves and the env setting KDE_FORK_SLAVES=1, I noticed that the helper process kio_http_cache_cleaner was started but not finished. This leads to problems with safely removing the stick for portable installations that were started from a USB stick, for example. In KDE4 times, this (and other) process(es) were terminated by the `kdeinit4 --shutdown` command after detecting that the main application had been terminated. The listed detection was done by a KDE autostart application called `kwinshutdown` from the package kdebase-runtime, which was started in the background via the automatic execution of `kdeinit` on main application startup. For KF5 single application packages on Windows, as currently provided by the KDE CI, there should also be corresponding possibilities to automatically terminate background programs (such as `kio_http_cache_cleaner`) when the main application is terminated. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439918] New: Impossible to edit individual widgets in the panel via touch
https://bugs.kde.org/show_bug.cgi?id=439918 Bug ID: 439918 Summary: Impossible to edit individual widgets in the panel via touch Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: herzensch...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 While it is possible to enter edit mode by press-and-hold in the desktop, it is not possible to edit currently existing widgets. One would expect this functionality to be available by press-and-hold on top of each widget. This sort of functionality would also allow to remove or replace widgets, especially useful when don't have access to a mouse or touchpad, which is usually the case for tablets. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439906] Provide a way to apply old wallpapers
https://bugs.kde.org/show_bug.cgi?id=439906 --- Comment #2 from medin --- The problem is that the upgrade forces the system to change the wallpaper which is not anticipated by user, and at the end user should search through some sort of third party to find that lost wallpaper, something is wrong ! This is not user friendly at all, the root cause is that the user choose the default wallpaper as most preferable background but got tricked after upgrading. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439917] New: Sometimes unable to rearrange pinned apps via touch
https://bugs.kde.org/show_bug.cgi?id=439917 Bug ID: 439917 Summary: Sometimes unable to rearrange pinned apps via touch 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: herzensch...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 If you rearrange panel app icons enough times with touch, it stops working. I didn't manage to find out how to reproduce it. In one of my tests it even happens immediately after login. Sometimes opening an application pinned to the panel allows you to drag apps again, but while this does occur with certain reliability, it's not 100%. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439904] Unable to decrypt PGP message sent via ProtonMail
https://bugs.kde.org/show_bug.cgi?id=439904
--- Comment #2 from Richard Weinberger ---
With this massiv hack I managed kmail to decrypt such messages:
diff --git a/mimetreeparser/src/bodyformatter/multipartmixed.cpp
b/mimetreeparser/src/bodyformatter/multipartmixed.cpp
index 00b90e121cf5..226909cef8d9 100644
--- a/mimetreeparser/src/bodyformatter/multipartmixed.cpp
+++ b/mimetreeparser/src/bodyformatter/multipartmixed.cpp
@@ -21,6 +21,9 @@
#include "objecttreeparser.h"
#include "messagepart.h"
+#include "utils.h"
+
+#include "bodyformatter/multipartencrypted.h"
#include
@@ -44,6 +47,14 @@ MessagePart::Ptr
MultiPartMixedBodyPartFormatter::process(Interface::BodyPart
return MessagePart::Ptr();
}
+// if the container contains a PGP part, assume it is some PGP mail and
re-inject
+// it into the MultiPartEncryptedBodyPartFormatter.
+if (findTypeInDirectChilds(part.content(), "application/pgp-encrypted")) {
+const auto formatter = MultiPartEncryptedBodyPartFormatter::create();
+qCWarning(MIMETREEPARSER_LOG) << "Found a application/pgp-encrypted
child";
+return formatter->process(part);
+}
+
// normal treatment of the parts in the mp/mixed container
MimeMessagePart::Ptr mp(new MimeMessagePart(part.objectTreeParser(),
part.content()->contents().at(0), false));
return mp;
I had also to disable the ApplicationGnuPGWKSPlugin plugin from kdepim-addons.
ApplicationGnuPGWKSPlugin completely voids MultiPartMixedBodyPartFormatter. But
that's a different issue, I guess.
--
You are receiving this mail because:
You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 --- Comment #59 from David Edmundson --- Please can someone insert this in their env (really really early, like /etc/profile.d/) QT_LOGGING_RULES=org.kde.powerdevil.debug=true and try and get me some logs. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 --- Comment #58 from David Edmundson --- That is really useful information, we've constantly been debugging races in plasmashell <--> powerdevil not powerdevil <--> upower -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 --- Comment #57 from Sam Edwards --- It appears that a restart of powerdevil does cause the battery applet to appear. Are there any logging settings I should consider turning on? It feels like powerdevil/plasmashell are deciding that my laptop is really a desktop (i.e. no battery) when first deciding whether to instantiate the battery applet, as a result of not yet discovering the battery. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409644] [Wayland] Panning in Okular is laggy with 4K monitor
https://bugs.kde.org/show_bug.cgi?id=409644 --- Comment #10 from Filzmaier Josef --- Created a MR: https://invent.kde.org/graphics/okular/-/merge_requests/458 -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 362437] Problem with the onion skin when inserting new keyframes (and some onion skin's issues)
https://bugs.kde.org/show_bug.cgi?id=362437 theaquaanimegirl...@gmail.com changed: What|Removed |Added CC||theaquaanimegirl123@gmail.c ||om -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 439916] New: Latte crashes whenever there is a widget reloading
https://bugs.kde.org/show_bug.cgi?id=439916 Bug ID: 439916 Summary: Latte crashes whenever there is a widget reloading Product: kde Version: unspecified Platform: Neon Packages OS: Linux Status: REPORTED Keywords: drkonqi Severity: crash Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: mateush.honor...@gmail.com Target Milestone: --- Application: latte-dock (0.9.12) Qt Version: 5.15.3 Frameworks Version: 5.84.0 Operating System: Linux 5.8.0-59-generic x86_64 Windowing System: X11 Drkonqi Version: 5.22.3 Distribution: KDE neon User Edition 5.22 -- Information about the crash: - What I was doing when the application crashed: I was connecting with a bluetooth device from the system tray added on a Latte panel, and the entire Latte application crashed. - Unusual behavior I noticed: This also happens while interacing with some other widgets sometimes, whenever something is loading. - Additional Information: I have the plasma-systray-latte-tweaks added, but I've already tried to remove it and the problem persists. The crash can be reproduced sometimes. -- Backtrace: Application: Latte Dock (latte-dock), signal: Segmentation fault [New LWP 4034] [New LWP 4036] [New LWP 4037] [New LWP 4038] [New LWP 4039] [New LWP 4040] [New LWP 4047] [New LWP 5071] [New LWP 5072] [New LWP 5074] [New LWP 5075] [New LWP 5076] [New LWP 5078] [New LWP 5095] [New LWP 5118] [New LWP 5119] [New LWP 5122] [New LWP 5167] [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". futex_wait_cancelable (private=, expected=0, futex_word=0x5572938d5bf0) at ../sysdeps/nptl/futex-internal.h:183 [Current thread is 1 (Thread 0x7fb63c5f9980 (LWP 4033))] Thread 19 (Thread 0x7fb5c976b700 (LWP 5167)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55728e0946d4) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55728e094680, cond=0x55728e0946a8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55728e0946a8, mutex=0x55728e094680) at pthread_cond_wait.c:647 #3 0x7fb6409d8f2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb64283cb44 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fb64283cfb9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fb6409d2dbc in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb63f87c609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb640504293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 18 (Thread 0x7fb5ca242700 (LWP 5122)): #0 __GI___libc_read (nbytes=16, buf=0x7fb5ca241a10, fd=57) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=57, buf=0x7fb5ca241a10, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fb63ebc2b2f in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x7fb63eb79ebe in g_main_context_check () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x7fb63eb7a312 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x7fb63eb7a4a3 in g_main_context_iteration () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x7fb640c13fcb in QEventDispatcherGlib::processEvents(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb640bb825b in QEventLoop::exec(QFlags) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #8 0x7fb6409d1c22 in QThread::exec() () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #9 0x7fb6409d2dbc in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x7fb63f87c609 in start_thread (arg=) at pthread_create.c:477 #11 0x7fb640504293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 17 (Thread 0x7fb5eccba700 (LWP 5119)): #0 futex_wait_cancelable (private=, expected=0, futex_word=0x55729b8473f0) at ../sysdeps/nptl/futex-internal.h:183 #1 __pthread_cond_wait_common (abstime=0x0, clockid=0, mutex=0x55729b8473a0, cond=0x55729b8473c8) at pthread_cond_wait.c:508 #2 __pthread_cond_wait (cond=0x55729b8473c8, mutex=0x55729b8473a0) at pthread_cond_wait.c:647 #3 0x7fb6409d8f2b in QWaitCondition::wait(QMutex*, QDeadlineTimer) () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #4 0x7fb64283cb44 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #5 0x7fb64283cfb9 in () at /lib/x86_64-linux-gnu/libQt5Quick.so.5 #6 0x7fb6409d2dbc in () at /lib/x86_64-linux-gnu/libQt5Core.so.5 #7 0x7fb63f87c609 in start_thread (arg=) at pthread_create.c:477 #8 0x7fb640504293 in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:95 Thread 16 (Thread 0x7fb5ee702700 (LWP 5118)): #0 __GI___libc_read (nbytes=16, buf=0x7fb5ee7019f0, fd=53) at ../sysdeps/unix/sysv/linux/read.c:26 #1 __GI___libc_read (fd=53, buf=0x7fb5ee7019f0, nbytes=16) at ../sysdeps/unix/sysv/linux/read.c:24 #2 0x7fb63ebc2b2f in () at
[dolphin] [Bug 439909] Searching in current directory doesn't work alt all
https://bugs.kde.org/show_bug.cgi?id=439909 tagwer...@innerjoin.org changed: What|Removed |Added CC||tagwer...@innerjoin.org --- Comment #4 from tagwer...@innerjoin.org --- (In reply to Piotr Mierzwinski from comment #0) > Created attachment 140099 [details] This says Status: Not Running, 0% complete If baloo was stopped it would not notice and index files you've just added. It could be you are seeing Bug 436352, where the indexer is paused but the button still says "Pause Indexer". You can try a "balooctl status" from the command line to see what it thinks the state of the indexer is or press the "Pause Indexer" button. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 439865] kf5.kio.core: couldn't create slave: "Meldung von klauncher: Unbekanntes Protokoll „g“.\n"
https://bugs.kde.org/show_bug.cgi?id=439865 --- Comment #3 from Ralf Habacker --- (In reply to Ahmad Samir from comment #2) > Is klauncher available on windows? IIRC kate explicitly runs on windows by > forking the slaved (probably setting KDE_FORK_SLAVES=1). Builds from binary factory are not using klauncher by default, as on the cmake command line used to compile kio, KDE_FORK_SLAVES=1 is set. Also klauncher is not packaged. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439915] New: No feedback when dragging app from menu to panel when using touch
https://bugs.kde.org/show_bug.cgi?id=439915 Bug ID: 439915 Summary: No feedback when dragging app from menu to panel when using touch Product: plasmashell Version: master Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: k...@davidedmundson.co.uk Reporter: herzensch...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Attempting to drag an app from the menu to the panel using a touchscreen doesn't show any sort of feedback indicating you managed to "grab" the app you want. It doesn't matter if it's from a grid or a list. -- You are receiving this mail because: You are watching all bug changes.
[kmymoney] [Bug 439883] onlinequoteeditor5 not included in kmymoney binaries generated by KDE CI
https://bugs.kde.org/show_bug.cgi?id=439883 Ralf Habacker changed: What|Removed |Added Severity|normal |wishlist --- Comment #1 from Ralf Habacker --- I just recognized that the online quotes editor is already available for Windows at at https://binary-factory.kde.org/job/Alkimia_Nightly_win64/, so that would an alternative to this feature request. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 422111] Battery applet not showing up in tray.
https://bugs.kde.org/show_bug.cgi?id=422111 --- Comment #56 from David Edmundson --- Asking a different question, does restarting powerdevil after an issue fix it? -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439906] Provide a way to apply old wallpapers
https://bugs.kde.org/show_bug.cgi?id=439906 David Edmundson changed: What|Removed |Added CC||k...@davidedmundson.co.uk Resolution|--- |NOT A BUG Status|REPORTED|RESOLVED --- Comment #1 from David Edmundson --- Old wallpapers are placed on the store. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-krunner] [Bug 439914] New: KRunner/Kickoff should always show results while typing with virtual keyboard
https://bugs.kde.org/show_bug.cgi?id=439914 Bug ID: 439914 Summary: KRunner/Kickoff should always show results while typing with virtual keyboard Product: frameworks-krunner Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: alexander.loh...@gmx.de Reporter: herzensch...@gmail.com Target Milestone: --- SUMMARY When searching the new menu Kickoff or KRunner (I believe both use the same backend) using a virtual keyboard, they don't show results while typing (or after typing). Not showing results while typing: - always happens with the menu - if KRunner is empty, it always happens - if KRunner is not empty (due to saving last search), it never happens - if KRunner is not empty, but you manually delete the current contents, it never happens STEPS TO REPRODUCE 1. Ensure there is no last search resting in KRunner 2. Enable virtual keyboard in the tray 3. Open KRunner 4. Type the name of any existing application in your system OBSERVED RESULT 1. No results are shown while and after typing, and 2. Pressing Enter opens the first result even if invisible EXPECTED RESULT 1. Results are shown while and after typing -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 439913] iNaturalist Export "Unknown Error" when click in Identification field
https://bugs.kde.org/show_bug.cgi?id=439913 Gary Hundt changed: What|Removed |Added CC||ghu...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 439913] New: iNaturalist Export "Unknown Error" when click in Identification field
https://bugs.kde.org/show_bug.cgi?id=439913 Bug ID: 439913 Summary: iNaturalist Export "Unknown Error" when click in Identification field Product: digikam Version: 7.3.0 Platform: Microsoft Windows OS: Microsoft Windows Status: REPORTED Severity: normal Priority: NOR Component: Plugin-WebService-iNaturalist Assignee: digikam-bugs-n...@kde.org Reporter: ghu...@gmail.com Target Milestone: --- SUMMARY iNaturalist Export "Unknown Error" when click in Identification field STEPS TO REPRODUCE 1. ensure you've registered your iNaturalist account info into digiKam first 2. select one or a few jpg files (with valid date and GPS info and under 2000px per side dimension) 3. open "Export to iNaturalist" dialog 4. click in "Enter Identification" field 5. click "OK" to the "Unknown Error" message 6. at the cursor in the "enter ID" field, type in a taxon and select one of the iNat suggestions returned 7. click the "start uploading" button, wait 8. click "OK" to the (2nd) "Unknown Error" message OBSERVED RESULT at 4. an "Error - digiKam" pops up with "Unknown Error" message. at 7. another "Error - digiKam" pops up with "Unknown Error" message. (If the "resize image" check box is checked, there is a short delay before the error pops up.) The green progress bar shows 50% (if selected one photo, or 25% if selected 3 photos) but that progress never changes. If you now go to your iNat account directly, a new observation has been created but no image attached. Each time you repeat these steps, a new observation record created with the chosen taxa ID shown but without image(s). Also, whether or not the "write Photo-ID" to Source Image" is checked, I see no added ID info in the source image metadata. EXPECTED RESULT no error msgs, create iNat Observation record with attached image(s), see chosen taxa ID added to caption or description or keyword fields in source jpg file. SOFTWARE/OS VERSIONS Windows: 10 Pro 21H1 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.
[gwenview] [Bug 439912] New: Gwenview Permission Problem
https://bugs.kde.org/show_bug.cgi?id=439912 Bug ID: 439912 Summary: Gwenview Permission Problem Product: gwenview Version: unspecified Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: importer Assignee: gwenview-bugs-n...@kde.org Reporter: doug.robert...@gmail.com Target Milestone: --- Upon insertion of my SD card a clickable Gwenview message pops up which should allow me to import photos. But at the same time: there is an error message saying I do not have permission to mount the SD card. I need to get my photos of off my card I was able to do that consistently right up until the KDE 5.22.3 update. After that any further attempt to import photos from the SD card gives me no response whatsoever. HELP STEPS TO REPRODUCE 1. Insert SD card 2. Look for pop up saying I can import photos via Gwenview 3. Read message saying: I do not have permission to mount the SD card. OBSERVED RESULT Permissions error message EXPECTED RESULT Gwenview allowing me to import photos as I was able to do before updating to 5.22.3 SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Manjaro Linux (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439909] Searching in current directory doesn't work alt all
https://bugs.kde.org/show_bug.cgi?id=439909 Piotr Mierzwinski changed: What|Removed |Added Resolution|FIXED |NOT A BUG -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439911] New: Popup virtual keyboard as a new action
https://bugs.kde.org/show_bug.cgi?id=439911 Bug ID: 439911 Summary: Popup virtual keyboard as a new action Product: systemsettings Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_kwintouchscreen Assignee: kwin-bugs-n...@kde.org Reporter: herzensch...@gmail.com CC: plasma-b...@kde.org Target Milestone: --- GNOME's virtual keyboard allows to show the virtual keyboard by swiping from the bottom edge upwards while keeping focus in the current window, and swiping from the top of the virtual keyboard downwards hides the keyboard. The first works around misbehaving apps who do not cooperate with virtual keyboards and never show them even if running natively on wayland (like Chrome/ium). With Maliit only the second action is possible. My first instinct is that this could be implemented as another action in the Touchscreen KCM. This also seems like consistent behavior in case the user wants to hide the keyboard to see the whole screen before getting back to writing, but perhaps this is best implemented in maliit itself. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439909] Searching in current directory doesn't work alt all
https://bugs.kde.org/show_bug.cgi?id=439909 Piotr Mierzwinski changed: What|Removed |Added Resolution|--- |FIXED Status|REPORTED|NEEDSINFO --- Comment #3 from Piotr Mierzwinski --- Ok. I retested it on different account and turned out that searching works. Only from some unknown reason it doesn't work on my regular account. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 439910] New: Scroll with touch in Konsole
https://bugs.kde.org/show_bug.cgi?id=439910 Bug ID: 439910 Summary: Scroll with touch in Konsole Product: konsole Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: herzensch...@gmail.com Target Milestone: --- Konsole, Yakuake and other terminals like the embedded one in Dolphin and Kate should allow to scroll with touchscreens (for instance, with two fingers so text is still selectable with one finger). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439909] Searching in current directory doesn't work alt all
https://bugs.kde.org/show_bug.cgi?id=439909 --- Comment #2 from Piotr Mierzwinski --- Created attachment 140101 --> https://bugs.kde.org/attachment.cgi?id=140101=edit dolphin - search 2 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439909] Searching in current directory doesn't work alt all
https://bugs.kde.org/show_bug.cgi?id=439909 Piotr Mierzwinski changed: What|Removed |Added CC||piotr.mierzwin...@gmail.com --- Comment #1 from Piotr Mierzwinski --- Created attachment 140100 --> https://bugs.kde.org/attachment.cgi?id=140100=edit dolphin - search 1 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439909] New: Searching in current directory doesn't work alt all
https://bugs.kde.org/show_bug.cgi?id=439909 Bug ID: 439909 Summary: Searching in current directory doesn't work alt all Product: dolphin Version: 21.04.3 Platform: Archlinux Packages OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: search Assignee: dolphin-bugs-n...@kde.org Reporter: piotr.mierzwin...@gmail.com CC: kfm-de...@kde.org Target Milestone: --- Created attachment 140099 --> https://bugs.kde.org/attachment.cgi?id=140099=edit file search - options SUMMARY I opened directory "~/Documents" to find file which I recently saved here. I was very surprise when after using Ctrl+F and putting name of this file I saw blank view. I closed it and started search manually, just typing first letters. I found my file in this way. I wonder why I wasn't to do it by "Search" option. I thought that maybe baloo didn't update its index yet for this directory, so I also tried to do it next day. Unfortunately with the same result. Notice that "File Search" is turned on (details on the screen shot). Some time ago I added my home directory, and found it there with status "indexed". I also added several other directories, which are "Not indexed", because they are mounted by nfs. In this list there is no "~/Documents" Additionally I tried to find file which is present in my home directory (which has status "Indexed"). Result the same as previously - blank view. Because of this my conclusion is: searching in dolphin doesn't work. STEPS TO REPRODUCE 1. Add your home directory to be indexed to "Search settings" 2. Save any file in ~/Documents, for example "my_document.pdf" 3. open dolphin, and go to "~/Documents" directory 4. press "Ctrl+F" and paste name of your file OBSERVED RESULT blank view EXPECTED RESULT file which was searched SOFTWARE/OS VERSIONS Linux/KDE Plasma: YES (available in About System) KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84 Qt Version: 5.15.2 with latest kde patches ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439908] New: Krita to support emojis in text entry
https://bugs.kde.org/show_bug.cgi?id=439908 Bug ID: 439908 Summary: Krita to support emojis in text entry Product: krita Version: 4.4.3 Platform: Other OS: Microsoft Windows Status: REPORTED Severity: wishlist Priority: NOR Component: Tool/Text Assignee: krita-bugs-n...@kde.org Reporter: rascon...@gmail.com Target Milestone: --- Created attachment 140098 --> https://bugs.kde.org/attachment.cgi?id=140098=edit result of the introduction of the emoji SUMMARY STEPS TO REPRODUCE 1. select text button 2. create text region 3. open text box 4. enter an emoji with win+. 5. save OBSERVED RESULT invisible red square EXPECTED RESULT SOFTWARE/OS VERSIONS Windows: 10 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.
[Elisa] [Bug 439907] New: Add search text field to filter the playlist titles
https://bugs.kde.org/show_bug.cgi?id=439907 Bug ID: 439907 Summary: Add search text field to filter the playlist titles Product: Elisa Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: matthieu_gall...@yahoo.fr Reporter: liubomi...@gmail.com Target Milestone: --- SUMMARY I have a suggestion. Like we can now filter the tracks in a folder, i suggest to also be able to filter the tracks in a playlist on the right / the ones scheduled to play. -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439896] magnetic selection tool crash
https://bugs.kde.org/show_bug.cgi?id=439896 Ahab Greybeard changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439896] magnetic selection tool crash
https://bugs.kde.org/show_bug.cgi?id=439896 --- Comment #3 from sly --- Error occurred on Thursday, July 15, 2021 at 10:21:00. krita.exe caused an Access Violation at location 7FFED21934C3 in module kritaselectiontools.dll Reading from location 0018. AddrPC Params 7FFED21934C3 0AFBF978 7FFECDE9D180 0AFBF978 kritaselectiontools.dll!0x434c3 QVector::~QVector+0x3 7FFED217F512 7FFECDE9CAE0 0002 kritaselectiontools.dll!0x2f512 KisToolSelectMagnetic::updateSelectedAnchor+0x112 7FFED2180DD5 005FB280 184D3AE0 184D3AE0 kritaselectiontools.dll!0x30dd5 KisToolSelectMagnetic::endPrimaryAction+0x315 7FFECCC49539 000E 7FFED3DD4DA0 0009 libkritaui.dll!0x39539 KisToolProxy::forwardToTool+0x99 7FFECCC49756 118DBC70 4E7645B0 179ACDF0 libkritaui.dll!0x39756 KisToolProxy::forwardEvent+0x146 7FFECCED085C 006002AC 0001 005FB560 libkritaui.dll!0x2c085c KisToolInvocationAction::end+0x8c 7FFECCEDCB2E 0028 005FB440 libkritaui.dll!0x2ccb2e KisShortcutMatcher::tryEndRunningShortcut+0xae 7FFECCEDED43 0C8F51D0 0001 005FB5C0 libkritaui.dll!0x2ced43 KisShortcutMatcher::buttonReleased+0x73 7FFECCEC70E9 279D9440 279D9440 005FB5E0 libkritaui.dll!0x2b70e9 KisInputManager::eventFilterImpl+0x569 7FFEF453C6C0 005FFB80 0001 1C050BE0 Qt5Core.dll!0x1fc6c0 QCoreApplication::applicationVersionChanged+0x1a0 7FFED3D97BB5 118BBA30 0003 018203B1 Qt5Widgets.dll!0x7bb5 QApplicationPrivate::notify_helper+0x75 7FFED3D9FC1A 7FFEF43625BF Qt5Widgets.dll!0xfc1a QApplication::notify+0x13aa 7FFECCF3E026 3FF0 C058C000 libkritaui.dll!0x32e026 KisApplication::notify+0x16 7FFEF453DDB8 3FF0 Qt5Core.dll!0x1fddb8 QCoreApplication::sendSpontaneousEvent+0x1a8 7FFED3D9E018 0030 0010 006A Qt5Widgets.dll!0xe018 QApplicationPrivate::sendMouseEvent+0x208 7FFED3DEA95D 0288AA70 7FFEF453C5C1 02960750 Qt5Widgets.dll!0x5a95d QDesktopWidget::qt_metacall+0x26fd 7FFED3DED6DB 005FFB80 02809C50 0001 Qt5Widgets.dll!0x5d6db QDesktopWidget::qt_metacall+0x547b 7FFED3D97BDC 153C97B0 2EB2C000 11848460 Qt5Widgets.dll!0x7bdc QApplicationPrivate::notify_helper+0x9c 7FFED3D9EC23 0288AA70 7FFEF43625BF Qt5Widgets.dll!0xec23 QApplication::notify+0x3b3 7FFECCF3E026 2EB2C1C0 7FFEF3D6A754 0288AA70 libkritaui.dll!0x32e026 KisApplication::notify+0x16 7FFEF453DDB8 0001 005FC550 0001 Qt5Core.dll!0x1fddb8 QCoreApplication::sendSpontaneousEvent+0x1a8 7FFEF3D56DC4 7FFEF4543B53 8012 Qt5Gui.dll!0x36dc4 QGuiApplicationPrivate::processMouseEvent+0x6e4 7FFEF3D58135 0290F460 02960950 000708AC Qt5Gui.dll!0x38135 QGuiApplicationPrivate::processWindowSystemEvent+0x105 7FFEF3D30EAC 0401 000708AC Qt5Gui.dll!0x10eac QWindowSystemInterface::sendWindowSystemEvents+0x44c 7FFEF45985EA 0001 0001 Qt5Core.dll!0x2585ea QEventDispatcherWin32Private::sendTimerEvent+0x60a 7FFF3B5AE858 0290F460 7FFEF4598110 000708AC USER32.dll!0xe858 UserCallWinProcCheckWow+0x2f8 7FFF3B5AE299 7FFEF4598110 005FC6F0 USER32.dll!0xe299 DispatchMessageWorker+0x249 7FFEF4597A8B 02960950 0024 0281C540 Qt5Core.dll!0x257a8b QEventDispatcherWin32::processEvents+0x5cb 6A8FF005 0080 0014 1B9EF240 qwindows.dll!0x7f005 qt_plugin_instance+0x2a25 7FFEF453BD9F 0CAC1470 0C8AB990 17992F60 Qt5Core.dll!0x1fbd9f QEventLoop::exec+0x13f 7FFEF4545017 005FFBD0 005FFB40 0010 Qt5Core.dll!0x205017 QCoreApplication::exec+0x77 000140006F4A 0001 02809BB0 000140F65970 krita.exe!0x6f4a main+0x213a 0001400013C7 krita.exe!0x13c7 __tmainCRTStartup+0x247 0001400014CB krita.exe!0x14cb WinMainCRTStartup+0x1b 7FFF3B7E7034 KERNEL32.DLL!0x17034 BaseThreadInitThunk+0x14 7FFF3C442651 ntdll.dll!0x52651 RtlUserThreadStart+0x21 00014000-000140FB3000 krita.exe 7FFF3C3F-7FFF3C5E5000 ntdll.dll 6.2.19041.1110 7FFF3B7D-7FFF3B88D000
[frameworks-kio] [Bug 439865] kf5.kio.core: couldn't create slave: "Meldung von klauncher: Unbekanntes Protokoll „g“.\n"
https://bugs.kde.org/show_bug.cgi?id=439865 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com --- Comment #2 from Ahmad Samir --- Is klauncher available on windows? IIRC kate explicitly runs on windows by forking the slaved (probably setting KDE_FORK_SLAVES=1). -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 439877] Dolphin crashes when right-clicking on file or folder to summon the contextual menu
https://bugs.kde.org/show_bug.cgi?id=439877 --- Comment #4 from Paul Brown --- (In reply to Harald Sitter from comment #2) > Git commit 07d54af0b6e3f074a9e679db506fc538f52cc410 by Harald Sitter. > Committed on 15/07/2021 at 14:01. > Pushed by sitter into branch 'release/21.08'. > > don't auto deduce QStringBuilder > > see 'auto QString(Builder) considered VERY HARMFUL' thread on kde-devel > https://markmail.org/message/mbrp5ypyhcfk7zjn > > What happens is that the type of str ends up being QStringBuilder > instead of QString. The QStringBuilder is destroyed after the semicolon, > and all access to "str" produces undefined behavior. > > Never use auto for QString concatenation! > > M +1-1 > activities/fileitemplugin/FileItemLinkingPluginActionLoader.cpp > > https://invent.kde.org/network/kio-extras/commit/ > 07d54af0b6e3f074a9e679db506fc538f52cc410 Thanks, Harald! -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 409644] [Wayland] Panning in Okular is laggy with 4K monitor
https://bugs.kde.org/show_bug.cgi?id=409644 Albert Astals Cid changed: What|Removed |Added CC||aa...@kde.org --- Comment #9 from Albert Astals Cid --- Those kWarnings need to be changed to qWarning -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 410074] Kio client error when mounting an external storage drive
https://bugs.kde.org/show_bug.cgi?id=410074 Ahmad Samir changed: What|Removed |Added CC||a.samir...@gmail.com Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO --- Comment #4 from Ahmad Samir --- Is this still an issue? -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 439896] magnetic selection tool crash
https://bugs.kde.org/show_bug.cgi?id=439896 --- Comment #2 from sly --- I just select the tool then try to use it. It either doesn't work then Krita crashes or some times it works at first but then things freeze up and then crash. On Thu, Jul 15, 2021, 12:37 PM Ahab Greybeard wrote: > https://bugs.kde.org/show_bug.cgi?id=439896 > > Ahab Greybeard changed: > >What|Removed |Added > > > CC| > |ahab.greybe...@hotmail.co.u >||k > Status|REPORTED|NEEDSINFO > Resolution|--- |WAITINGFORINFO > > --- Comment #1 from Ahab Greybeard --- > The attachment shows the session logs which do not indicate a crash. > Can you attach the crash log which is at > C:\Users\shelb\AppData\Local\kritacrash.log? > > Can you replicate the crash and describe details of which particular > actions > cause the crash? > > -- > You are receiving this mail because: > You reported the bug. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-solid] [Bug 409207] dolphin / device manager can't mount usb disks
https://bugs.kde.org/show_bug.cgi?id=409207 Ahmad Samir changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||a.samir...@gmail.com --- Comment #1 from Ahmad Samir --- Is this still an issue? -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439904] Unable to decrypt PGP message sent via ProtonMail
https://bugs.kde.org/show_bug.cgi?id=439904 --- Comment #1 from Richard Weinberger --- I think I've found the root cause. The very first like of ProtonMail encrypted mails are "Content-Type: multipart/mixed;". When I manually change this line to "Content-Type: multipart/encrypted;" Kmail is able to decrypt the message. -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 439906] New: Provide a way to apply old wallpapers
https://bugs.kde.org/show_bug.cgi?id=439906 Bug ID: 439906 Summary: Provide a way to apply old wallpapers Product: systemsettings Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: kcm_desktoptheme Assignee: plasma-b...@kde.org Reporter: med.medin.2...@gmail.com Target Milestone: --- When I used 5.21 I had applied Dark Breeze theme and the default wallpaper was perfect combination with it (easy on eyes), but after upgrading I got a new wallpaper that hurts my eyes with its whiteness and it's completely incompatible with Dark Breeze theme, I wish if there is a way to retain those great old wallpapers or at least provide with each release two versions of the default wallpaper : one suitable for light theme and another for dark theme. NB : The same for Screen Lock and SDDM wallpapers. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439905] New: SDDM retains 5.21 default wallpaper after upgrading
https://bugs.kde.org/show_bug.cgi?id=439905 Bug ID: 439905 Summary: SDDM retains 5.21 default wallpaper after upgrading Product: plasmashell Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Lock/logout Assignee: plasma-b...@kde.org Reporter: med.medin.2...@gmail.com Target Milestone: 1.0 After upgrading, SDDM still has the old wallpaper, while Lock screen and Desktop show the new wallpaper, when I check the SDDM theme settings it's set to default theme with preview of the new wallpaper, even if you select another theme and apply it then revert to default theme and also apply it, the login screen always shows the old 5.21 wallpaper. -- You are receiving this mail because: You are watching all bug changes.
[kmail2] [Bug 439904] New: Unable to decrypt PGP message sent via ProtonMail
https://bugs.kde.org/show_bug.cgi?id=439904 Bug ID: 439904 Summary: Unable to decrypt PGP message sent via ProtonMail Product: kmail2 Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: crypto Assignee: kdepim-b...@kde.org Reporter: richard-b...@nod.at Target Milestone: --- ProtonMail seems to encode PGP messages differently than Kmail (actually messagelib) expects. The MIME section of such a message looks like: --00bda24ff6a439c55df37bffe4bd232aad4d80072f16b06818700820c3d89297 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=utf-8 --00bda24ff6a439c55df37bffe4bd232aad4d80072f16b06818700820c3d89297 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=attachment.bin Content-Type: application/pgp-encrypted; name=attachment.bin X-Pm-Content-Encryption: end-to-end VmVyc2lvbjogMQ0K --00bda24ff6a439c55df37bffe4bd232aad4d80072f16b06818700820c3d89297 Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename=openpgp-encrypted-message.asc Content-Type: application/octet-stream; name=openpgp-encrypted-message.asc X-Pm-Content-Encryption: end-to-end LS0tLS1CRUdJTiBQR1AgTUVTU0FHRS0tLS0tDQoNCmhRSU1BK3B1cm93N0hWSHhBUS8vUXhGdTBS ... MORE BASE64... ... dDAwbA0KPTZOYmwNCi0tLS0tRU5EIFBHUCBNRVNTQUdFLS0tLS0NCg== --00bda24ff6a439c55df37bffe4bd232aad4d80072f16b06818700820c3d89297-- messagelib (any version) does not expect the "PGP/MIME version identification" message part being an attachment. Interestingly messagelib emits the following warning: org.kde.pim.mimetreeparser: Unknown PGP Version String: "-BEGIN PGP MESSAGE-.." Somehow the application/octet-stream part makes it into ApplicationPGPEncryptedBodyPartFormatter::process(). My KDE distribution is not super fresh but from checking the code I'm sure that no recent KDE/Kmail version is able to decrypt such an mail. SOFTWARE/OS VERSIONS Linux/KDE Plasma: openSUSE LEAP 15.2 (available in About System) KMail Version 5.14.2 (20.04.2) -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 439903] New: Opacity is not applied to Tray widgets and Widgets Adder
https://bugs.kde.org/show_bug.cgi?id=439903 Bug ID: 439903 Summary: Opacity is not applied to Tray widgets and Widgets Adder Product: plasmashell Version: 5.22.3 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Theme - Breeze Assignee: visual-des...@kde.org Reporter: med.medin.2...@gmail.com CC: plasma-b...@kde.org Target Milestone: 1.0 Created attachment 140095 --> https://bugs.kde.org/attachment.cgi?id=140095=edit Opacity is not applied to Tray widgets and Widgets Adder If you set panel opacity to Opaque then it will not be applied to Tray widgets and Widgets Adder. See attached image for more info. -- You are receiving this mail because: You are watching all bug changes.
