[frameworks-baloo] [Bug 470382] Baloo unable to index any files
https://bugs.kde.org/show_bug.cgi?id=470382 --- Comment #4 from tagwer...@innerjoin.org --- > ... change MemoryHigh works for me. According to status output from systemd, > baloo just hits the memory limited by systemd ... That was a lucky guess then :-) > Is that possible to output a warning when baloo failed to request more memory > as both systemd and baloo keep silence when it happened? >From reading, baloo doesn't get an immediate failure, it just gets pressure to release memory. The problem is that in this case baloo does need the memory (or thinks it does)... > But I also noticed Baloo doesn't seem to release memory after indexed. > Except that, is possible to find what file / reason it wants to index that > caused those high memory demand. My working assumption has been that you are seeing the memory used for "cached" info, the memory mapped bits of database. In the simple case, that's no problem, when there's memory pressure, the memory will be released (and the info read back from the disc again when called for). That's more complicated if you are wanting to write a transaction to disc, the memory will be flagged dirty and must be held in memory until committed. That's the way, I think, that LMDB works.. What happens though is that, when baloo does its initial sweep through the filesystems to build a list of what's changed and what's new, this information is handled as a single transaction. That's an "Ouch" when you've got a very large number of changes. There's a wonderful, eye watering example in Bug 394759 (scroll down to the 13th comment). Your note that you'd indexed over a million files was a clue... I'd say the MemoryHigh=50% is reasonable although it's a juggling act. You want to allow baloo enough space to do its initial indexing but it shouldn't impact the rest of the system The proper solution here would be for baloo to split up the work in its "first pass" and commit every 15 or 30 seconds rather than build up a single large transaction. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419421] QML timers go too fast with multi-threaded render loop when using any high refresh rate screens on X11 when using FOSS amdgpu drivers
https://bugs.kde.org/show_bug.cgi?id=419421 soredake changed: What|Removed |Added CC|broaden_acid002@simplelogin | |.com| -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 468856] KRunner remembers searches done through the application launcher
https://bugs.kde.org/show_bug.cgi?id=468856 --- Comment #4 from Alexander Lohnau --- Git commit 0e1b7e93f1bea769b865259b87adc75c726e0488 by Alexander Lohnau. Committed on 02/06/2023 at 05:19. Pushed by alex into branch 'master'. Allow use of different state config group This way, one can support different autocompletion groups when using the KRunner model. For example, if the Kicker and KRunner history should be handled separately. M +17 -0autotests/runnermanagertest.cpp M +9-3src/model/resultsmodel.cpp M +1-0src/model/resultsmodel.h M +2-2src/model/runnerresultsmodel.cpp M +2-1src/model/runnerresultsmodel_p.h M +11 -4src/runnermanager.cpp M +1-0src/runnermanager.h https://invent.kde.org/frameworks/krunner/-/commit/0e1b7e93f1bea769b865259b87adc75c726e0488 -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 470546] xdg-desktop-portal-kde starts too early, causing dbus reads to return incorrect values
https://bugs.kde.org/show_bug.cgi?id=470546 SC changed: What|Removed |Added CC||k...@scheimong.net -- You are receiving this mail because: You are watching all bug changes.
[xdg-desktop-portal-kde] [Bug 470546] New: xdg-desktop-portal-kde starts too early, causing dbus reads to return incorrect values
https://bugs.kde.org/show_bug.cgi?id=470546 Bug ID: 470546 Summary: xdg-desktop-portal-kde starts too early, causing dbus reads to return incorrect values Classification: Plasma Product: xdg-desktop-portal-kde Version: 5.27.5 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: plasma-b...@kde.org Reporter: k...@scheimong.net CC: aleix...@kde.org, jgrul...@redhat.com, n...@kde.org Target Milestone: --- # SUMMARY `qdbus org.freedesktop.portal.Desktop /org/freedesktop/portal/desktop org.freedesktop.portal.Settings.Read org.freedesktop.appearance color-scheme` is not correctly reporting the user's preferred theme (dark/light) after startup. Only after manually restarting `xdg-desktop-portal-kde` (`systemctl --user restart plasma-xdg-desktop-portal-kde.service`) does it work correctly. See here (https://invent.kde.org/plasma/xdg-desktop-portal-kde/-/merge_requests/52#note_691671) for how I ran into this problem + initial triage. # STEPS TO REPRODUCE 1. Make sure `xdg-desktop-portal` and `xdg-desktop-portal-kde` are installed 2. Set your KDE theme to `Breeze Dark` 3. Restart your OS 4. Run `qdbus org.freedesktop.portal.Desktop /org/freedesktop/portal/desktop org.freedesktop.portal.Settings.Read "org.freedesktop.appearance" "color-scheme"` 5. Run `systemctl --user restart plasma-xdg-desktop-portal-kde.service` 6. Repeat step 4 # OBSERVED RESULT The dbus query (step 4) prints 2. Then after restart, the same query (step 6) prints 1. # EXPECTED RESULT They should both print 1. # SOFTWARE/OS VERSIONS - OS: EndeavourOS with all updates (as of 2023-06-02) - Kernel: `6.3.5-arch1-1` - Display server: X11 - Plasma: `5.27.5` - Framework: `5.106.0` - Qt: `5.15.9` - xdg-desktop-portal: `1.16.0` - xdg-desktop-portal-kde: `5.27.5` # ADDITIONAL INFORMATION I tested this on several different systems at my disposal. The results are somewhat curious. - Both of my EndeavourOS KDE laptops have this issue - Neither of my two tested VMs have this issue, including: - EndeavourOS KDE - Fedora 38 KDE - I also have Debian 11 but it only has KDE `5.20.5`, so I was not able to test it Related bug: https://bugs.kde.org/show_bug.cgi?id=458865 -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 120192] Notarization of MacOS PKG Installer as Apple Store package - Use Craft Continuous Deployment System.
https://bugs.kde.org/show_bug.cgi?id=120192 --- Comment #25 from caulier.gil...@gmail.com --- A note about the native Apple Silicon architecture of the digiKam PKG. I receive a message from the maintainer of QElectroTech application, a free software to create electric diagrams based on Qt. Until now they only provide this application for Intel Apple computers, but they switch to Apple silicon and compile the PKG for M1/M2 arm64 cpu using the digiKam packaging scripts based on Macports, and it work... https://qelectrotech.org/forum/viewtopic.php?id=2393 This want mean than the script are mostly ready for packaging digiKam for Apple Silicon. Gilles -- You are receiving this mail because: You are watching all bug changes.
[krunner] [Bug 468856] KRunner remembers searches done through the application launcher
https://bugs.kde.org/show_bug.cgi?id=468856 Bug Janitor Service changed: What|Removed |Added Status|CONFIRMED |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/2969 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470545] New: definition lists not supported
https://bugs.kde.org/show_bug.cgi?id=470545 Bug ID: 470545 Summary: definition lists not supported Classification: Applications Product: okular Version: 23.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: markdown backend Assignee: okular-de...@kde.org Reporter: testing1237...@yahoo.com Target Milestone: --- Created attachment 159409 --> https://bugs.kde.org/attachment.cgi?id=159409=edit markdown file SUMMARY *** definition lists are supported by some markdown editors and viewers, it looks like okular does not support the same. https://www.markdownguide.org/extended-syntax/#definition-lists ``` First Term : This is the definition of the first term. Second Term : This is one definition of the second term. : This is another definition of the second term. ``` STEPS TO REPRODUCE 1. open the attached file in okular 2. compare with https://stackedit.io/app# or https://dillinger.io/ 3. OBSERVED RESULT rendering is not made properly EXPECTED RESULT just like the websites, the output should be rendered 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.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kig] [Bug 467718] cursor in construction is excruciatingly slow
https://bugs.kde.org/show_bug.cgi?id=467718 Bug Janitor Service changed: What|Removed |Added Resolution|WAITINGFORINFO |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #5 from Bug Janitor Service --- This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 425715] Rectangular Region: Spectacle sometimes hides window, but i can't select a region, when Compositor is suspended.
https://bugs.kde.org/show_bug.cgi?id=425715 Bug Janitor Service changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO |WORKSFORME --- Comment #9 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.
[kwin] [Bug 469864] Always on top is not respected
https://bugs.kde.org/show_bug.cgi?id=469864 --- Comment #8 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.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 432143] ssh config file with "includes" not taken into account
https://bugs.kde.org/show_bug.cgi?id=432143 Pedro V changed: What|Removed |Added CC||voidpointertonull+bugskdeor ||g...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kio] [Bug 392903] sftp doesn't work with hashed known_hosts file
https://bugs.kde.org/show_bug.cgi?id=392903 Pedro V changed: What|Removed |Added CC||voidpointertonull+bugskdeor ||g...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[knetattach] [Bug 284643] dolphin(sftp) doesn't follow the ssh config for instructions on connecting to hosts
https://bugs.kde.org/show_bug.cgi?id=284643 Pedro V changed: What|Removed |Added CC||voidpointertonull+bugskdeor ||g...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kio-extras] [Bug 470544] New: Many SSH config options are not respected
https://bugs.kde.org/show_bug.cgi?id=470544 Bug ID: 470544 Summary: Many SSH config options are not respected Classification: Frameworks and Libraries Product: kio-extras Version: unspecified Platform: unspecified OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: SFTP Assignee: plasma-b...@kde.org Reporter: voidpointertonull+bugskde...@gmail.com Target Milestone: --- This wishlist item is about the generic problem of the user's SSH config file options often not being respected. Marked it as a wish only because most of the SFTP logic lives outside of the project, so technically the problem is with an external project, but the issue keeps plaguing KDE projects for end users as can be seen from bug reports. The issue appears to be with libssh either being incredibly slow with implementing config option support, or simply possibly ignoring what may be seen as convenience options rarely used outside of interactive environments. A few examples of options not supported (marked with "SOC_UNSUPPORTED" in libssh): - HashKnownHosts - CheckHostIP - HostKeyAlias It seems like that most (easy to notice) issues are with how known_hosts is handled, both ignoring already present entries, and littering the file with new, redundant entries. This also presents a security issue as users of related unsupported options have to go through the trust on first use procedure of checking the identity of the SSH server again which is tempting to ignore due to the fatigue of theoretically redundant checks being presented due to already existing known_host entries not being matched. A few examples of related bug reports: - Bug 284643 - Bug 392903 - Bug 432143 -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 469757] kAlarm does not function if icon not present in system tray
https://bugs.kde.org/show_bug.cgi?id=469757 --- Comment #2 from bizdea...@protonmail.ch --- (In reply to David Jarvie from comment #1) > Is KAlarm still running after removing it from the system tray? > > Bear in mind that if "Show in system tray" is selected, closing the main > window will leave KAlarm running (in the system tray), but if "Show in > system tray" is NOT selected, closing the main window will cause KAlarm to > quit. So to keep using it while not showing it in the system tray, you have > to leave it running in the same way as other applications, so if you're > using a task manager in the panel, it will show there. What you mention is interesting because after closing both the system tray AND the main application, I still see a process in Task Manager called "kalarm --tray". Regardless, it appears that the feature I was hoping for is not supported. I was hoping to eventually kAlarm could become a background process -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 462860] Rectangle capture modes have wrong GUI sizing and positioning with fractional scaling
https://bugs.kde.org/show_bug.cgi?id=462860 Zeeko changed: What|Removed |Added CC||zeeko@gianthard.rocks -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[krita] [Bug 470531] [Android] SDLAudioManager crash
https://bugs.kde.org/show_bug.cgi?id=470531 sh_zam changed: What|Removed |Added Status|REPORTED|ASSIGNED CC||sh...@sdf.org Ever confirmed|0 |1 Assignee|krita-bugs-n...@kde.org |sh...@sdf.org -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 126942] Kghostview can't show any overprint preview
https://bugs.kde.org/show_bug.cgi?id=126942 --- Comment #5 from Bernard Gray --- Created attachment 159408 --> https://bugs.kde.org/attachment.cgi?id=159408=edit Comparison of PDF output with Overprint on vs off -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 126942] Kghostview can't show any overprint preview
https://bugs.kde.org/show_bug.cgi?id=126942 --- Comment #4 from Bernard Gray --- Created attachment 159407 --> https://bugs.kde.org/attachment.cgi?id=159407=edit PDF file requiring Overprint support to display correctly done! -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 470543] Continuous crackling
https://bugs.kde.org/show_bug.cgi?id=470543 Bernd changed: What|Removed |Added CC||bern...@yahoo.com --- Comment #1 from Bernd --- Did you check this: https://docs.kdenlive.org/en/troubleshooting/windows_issues.html -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 470477] Cannot create alarms
https://bugs.kde.org/show_bug.cgi?id=470477 --- Comment #4 from van.sny...@sbcglobal.net --- On Thu, 2023-06-01 at 20:34 +, David Jarvie wrote: > https://bugs.kde.org/show_bug.cgi?id=470477 > > --- Comment #3 from David Jarvie ---A possible fix > is to right click on the alarm calendar in the calendar viewpanel, > and ensure that "Use as default for active alarms" is selected. > However, if the calendar is already selected as default, or if it > still doesn'twork after doing that, I suggest deleting and re-adding > the alarm calendar asfollows: > 1) Select the active alarm calendar in the calendar view panel, and > click ShowDetails. Note the File location.2) Remove it from KAlarm's > database by clicking Remove. (Note that this doesn'tdelete your > actual alarm calendar file.)3) Add the calendar again by clicking > Add. In the dialog, enter the filelocation noted in step 1, select > Active Alarms, enter "Active Alarms" as thename, and do not select > read only. After doing both sets of steps, it still refuses to create alarms. The "Active Alarms" calendar is not read only. It is enabled, and is the default calendar. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 470484] Powerdevil crashes multiple times during screen sleep
https://bugs.kde.org/show_bug.cgi?id=470484 Nicolas Fella changed: What|Removed |Added CC||nicolas.fe...@gmx.de --- Comment #1 from Nicolas Fella --- Can you please follow https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl to get a proper backtrace? The one you pasted is missing demangling and debug symbols to be fully useful -- You are receiving this mail because: You are watching all bug changes.
[KScreen] [Bug 469160] kscreen-doctor segmentation faults in KIconLoader::~KIconLoader() when exiting
https://bugs.kde.org/show_bug.cgi?id=469160 Ryan Rix changed: What|Removed |Added CC||r...@n.rix.si --- Comment #3 from Ryan Rix --- This only happens when I am running kwin_wayland -- kwin_x11 does not exhibit this issue. in my case it's slightly different behavior but only occurs on kwin_wayland: ``` ~ $ kscreen-doctor --json warning: queue 0x1aec2f0 destroyed while proxies still attached: wl_display@1 still attached corrupted size vs. prev_size in fastbins aborted (core dumped) ``` Thread 1 (Thread 0x73cff880 (LWP 3617698) ".kscreen-doctor"): #0 0x76e21adc in __pthread_kill_implementation () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #1 0x76dd2cb6 in raise () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #2 0x76dbc8ba in abort () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #3 0x76dbd5f5 in __libc_message.cold () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #4 0x76e2b785 in malloc_printerr () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #5 0x76e2c04e in unlink_chunk.constprop () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #6 0x76e2d6cb in _int_free () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #7 0x76e2fe83 in free () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #8 0x7fffe4a2a3c3 in KIconTheme::~KIconTheme() () from /nix/store/d57as4xqqimmrisfn48nwx81hh7851ck-kiconthemes-5.106.0/lib/libKF5IconThemes.so.5 #9 0x7fffe4a22e7a in KIconLoaderPrivate::clear() () from /nix/store/d57as4xqqimmrisfn48nwx81hh7851ck-kiconthemes-5.106.0/lib/libKF5IconThemes.so.5 #10 0x7fffe4a2312e in KIconLoaderPrivate::~KIconLoaderPrivate() () from /nix/store/d57as4xqqimmrisfn48nwx81hh7851ck-kiconthemes-5.106.0/lib/libKF5IconThemes.so.5 #11 0x7fffe4a23398 in KIconLoader::~KIconLoader() () from /nix/store/d57as4xqqimmrisfn48nwx81hh7851ck-kiconthemes-5.106.0/lib/libKF5IconThemes.so.5 #12 0x7fffe4a233e9 in (anonymous namespace)::Q_QGS_globalIconLoader::innerFunction()::Holder::~Holder() () from /nix/store/d57as4xqqimmrisfn48nwx81hh7851ck-kiconthemes-5.106.0/lib/libKF5IconThemes.so.5 #13 0x76dd5285 in __run_exit_handlers () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #14 0x76dd53be in exit () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #15 0x76dbdad5 in __libc_start_call_main () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #16 0x76dbdb89 in __libc_start_main_impl () from /nix/store/yaz7pyf0ah88g2v505l38n0f3wg2vzdj-glibc-2.37-8/lib/libc.so.6 #17 0x00406165 in _start () Operating System: NixOS 23.11 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 Kernel Version: 6.1.30 (64-bit) Graphics Platform: Wayland Processors: 8 × Intel® Core™ i7-7700K CPU @ 4.20GHz Memory: 62.7 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 630 -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 470346] Out-of-bounds access in Screen::setSelectionEnd when selecting last line of scrolling text
https://bugs.kde.org/show_bug.cgi?id=470346 tcanabr...@kde.org changed: What|Removed |Added Resolution|--- |FIXED Status|ASSIGNED|RESOLVED Latest Commit||https://invent.kde.org/util ||ities/konsole/-/commit/2893 ||1090bcbcd577932f293c6e32cc5 ||935f2bda5 --- Comment #2 from tcanabr...@kde.org --- Git commit 28931090bcbcd577932f293c6e32cc5935f2bda5 by Tomaz Canabrava, on behalf of Luis Javier Merino Morán. Committed on 01/06/2023 at 06:24. Pushed by tcanabrava into branch 'master'. Adjust selection point coords when scrollback shrinks The selection point coordinates are relative to the start of the scrollback, so when the scrollback shrinks, either because it is limited to some amount of lines, or because it is cleared, we could end up with stale coordinates which could cause a crash on a subsequent selection extend operation. M +2-0src/Screen.cpp M +7-0src/terminalDisplay/TerminalDisplay.cpp M +1-0src/terminalDisplay/TerminalDisplay.h https://invent.kde.org/utilities/konsole/-/commit/28931090bcbcd577932f293c6e32cc5935f2bda5 -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419421] QML timers go too fast with multi-threaded render loop when using any high refresh rate screens on X11 when using FOSS amdgpu drivers
https://bugs.kde.org/show_bug.cgi?id=419421 cabanur changed: What|Removed |Added Version Fixed In||6.0 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 419421] QML timers go too fast with multi-threaded render loop when using any high refresh rate screens on X11 when using FOSS amdgpu drivers
https://bugs.kde.org/show_bug.cgi?id=419421 cabanur changed: What|Removed |Added CC||caba...@cabanur.com Version Fixed In|6.0 | -- You are receiving this mail because: You are watching all bug changes.
[kdenlive] [Bug 470543] New: Continuous crackling
https://bugs.kde.org/show_bug.cgi?id=470543 Bug ID: 470543 Summary: Continuous crackling Classification: Applications Product: kdenlive Version: 23.04.1 Platform: Other OS: Other Status: REPORTED Severity: normal Priority: NOR Component: Video Display & Export Assignee: j...@kdenlive.org Reporter: rat.pelleg...@gmail.com Target Milestone: --- SUMMARY *** Crackling noise even with no sound in the track I uninstalled reinstalled the app but it didn't change anything I've used this app before and it's never done this to me. *** STEPS TO REPRODUCE 1. Launch the app 2. start the video (even if there are no video) 3. OBSERVED RESULT - Continuous crackling EXPECTED RESULT - No continuous crackling 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.
[arts] [Bug 145921] I have crackling scratchy sound whenever sound is played all the way from start-up, shutdown, wav, mp3 or movie sound. I have a soundblaster sound card.
https://bugs.kde.org/show_bug.cgi?id=145921 rat.pelleg...@gmail.com changed: What|Removed |Added CC||rat.pelleg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 470451] 3 feature requests for KAlarm: "today selector", "see past alarms", "defer presets"
https://bugs.kde.org/show_bug.cgi?id=470451 --- Comment #2 from tata...@gmail.com --- To be honest, I think Thunderbird Calendar's interface is perfect for reminders, so that's what I'm going to suggest for the "today" control, and for you to maybe reconsider the usefulness of having presets for the defer options! https://i.imgur.com/v9iNXjF.png The reason I really like defer presets is that, most of the time, when I snooze an alarm, it's because I'm busy and don't have time to response to the alarm properly. I don't want to waste time, have to put the cursor in the right place to specify the defer amount, "oh no, I don't want to edit the hours, I want to edit the minutes!"... It is much easier, in my opinion, to select a preset and then immediately forget about the alarm. For the past alarms, I sometimes like to remember what an alarm was 2 days ago. "How much money did I have to send to Bob again?". Also, I'm not sure what the "Keep alarms after expiry" option does, to be honest. It doesn't seem to work for me. Maybe I'm missing something? By the way, the reason I no longer use Thunderbird for my reminders is that more than once I snoozed an alarm and it didn't pop up again! I'm not sure what exactly triggers this bug... But a reminder application cannot have this bug. It's pretty much the very first bug it cannot have! Thanks again! -- You are receiving this mail because: You are watching all bug changes.
[amarok] [Bug 230440] crackling with low bitrate
https://bugs.kde.org/show_bug.cgi?id=230440 rat.pelleg...@gmail.com changed: What|Removed |Added CC||rat.pelleg...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470542] New: [Dolphin] Custom User Commands
https://bugs.kde.org/show_bug.cgi?id=470542 Bug ID: 470542 Summary: [Dolphin] Custom User Commands Classification: Applications Product: dolphin Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: wishlist Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: advice2...@protonmail.com CC: kfm-de...@kde.org Target Milestone: --- Here is a really desired feature that would mean so much to me, hopefully others will desire this as well. KDE is so well known for all its customization / options and Linux is known for command line functionality that it seems like it is so meant to be, wouldn't think I would have to ask for this one. Looking to have the option added for users to be able to create their own custom toolbar buttons / commands / hotkeys assigned to them. KDE already has this functionality available, could basically take the overall idea right from Krusader which uses "ActionMan". This feature would add so much customization options to Dolphin. Anything you could do in a terminal, which in Linux is basically everything could be used. Would allow users to be able to pass files to all kinds of other applications and commands. The possibilities are endless! Context Menu / Services are nice and they do serve a purpose, but custom buttons and hotkeys would be on another level. They would provide customization,functionality and instant access to the commands assigned to them. I have seen a couple other file managers in Linux already adding this, yet this kind of customization has KDEs name all over it. This would be a very exciting feature to be added, hard to really find a reason not to add this one. Hopefully others agree, please vote for this one. Thank you to anyone who reads this. -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456504] When using the "double click to open files" setting, you need to click extremely fast on the deskop
https://bugs.kde.org/show_bug.cgi?id=456504 cabanur changed: What|Removed |Added CC|caba...@cabanur.com | -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 456504] When using the "double click to open files" setting, you need to click extremely fast on the deskop
https://bugs.kde.org/show_bug.cgi?id=456504 cabanur changed: What|Removed |Added CC||caba...@cabanur.com -- You are receiving this mail because: You are watching all bug changes.
[systemsettings] [Bug 154804] Add option for alternative Drag behaviour
https://bugs.kde.org/show_bug.cgi?id=154804 Christoph Feck changed: What|Removed |Added CC||loudsq...@tutanota.com --- Comment #59 from Christoph Feck --- *** Bug 454356 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454356] Allow the user to switch off the drag and drop context menu
https://bugs.kde.org/show_bug.cgi?id=454356 Christoph Feck changed: What|Removed |Added Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #2 from Christoph Feck --- *** This bug has been marked as a duplicate of bug 154804 *** -- You are receiving this mail because: You are watching all bug changes.
[NeoChat] [Bug 470541] New: Search bar causing overhang on sidebar
https://bugs.kde.org/show_bug.cgi?id=470541 Bug ID: 470541 Summary: Search bar causing overhang on sidebar Classification: Applications Product: NeoChat Version: 23.04.1 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: General Assignee: fe...@posteo.de Reporter: nat...@upchur.ch CC: c...@carlschwan.eu Target Milestone: --- Created attachment 159405 --> https://bugs.kde.org/attachment.cgi?id=159405=edit An image showing the issue SUMMARY There is an overhang onto the sidebar from beneath the search bar. SOFTWARE/OS VERSIONS Linux/KDE Plasma: EndeavourOS KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470540] Screen order is messed up after connecting an external display
https://bugs.kde.org/show_bug.cgi?id=470540 --- Comment #4 from leonardopsan...@gmail.com --- Followed the discussion here https://invent.kde.org/plasma/plasma-workspace/-/issues/52 And here https://invent.kde.org/plasma/plasma-workspace/-/issues/21 -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470540] Screen order is messed up after connecting an external display
https://bugs.kde.org/show_bug.cgi?id=470540 --- Comment #3 from leonardopsan...@gmail.com --- ls /sys/class/drm card0 card0-DP-1 card0-DP-2 card0-eDP-1 card0-HDMI-A-1 renderD128 version -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470540] Screen order is messed up after connecting an external display
https://bugs.kde.org/show_bug.cgi?id=470540 --- Comment #2 from leonardopsan...@gmail.com --- Created attachment 159404 --> https://bugs.kde.org/attachment.cgi?id=159404=edit xrandr output -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470540] Screen order is messed up after connecting an external display
https://bugs.kde.org/show_bug.cgi?id=470540 --- Comment #1 from leonardopsan...@gmail.com --- Created attachment 159403 --> https://bugs.kde.org/attachment.cgi?id=159403=edit Display configuration screenshot -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 470540] New: Screen order is messed up after connecting an external display
https://bugs.kde.org/show_bug.cgi?id=470540 Bug ID: 470540 Summary: Screen order is messed up after connecting an external display Classification: Plasma Product: plasmashell Version: 5.27.4 Platform: Ubuntu OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: generic-multiscreen Assignee: plasma-b...@kde.org Reporter: leonardopsan...@gmail.com CC: aleix...@kde.org, notm...@gmail.com Target Milestone: 1.0 Created attachment 159402 --> https://bugs.kde.org/attachment.cgi?id=159402=edit Panels and Desktops Management showing wrong screen order SUMMARY After disconnecting and re-connecting an external display, my panels end up on the wrong display. My setup is not very exotic: - Laptop attached screen - External HP Z27 (through a USB 3 Thunderbolt cable) - External HP Z27 (through an HDMI cable) I've added a KDE default panel to external USB monitor and an empty panel to the external HDMI monitor. I've added a task manager widget to the empty panel. TL; DR: the two external monitors have panels configured differently, so I can tell them apart. Looking at the "Panels and Desktops Management" app, I see that the order they appear (screenshot 1) is not the order that's configured (screenshot 2). Also, when I first configured everything, the laptop display was the leftmost screen on "Panels and Desktops Management" app, now is the rightmost. I've also attached the output of xrandr. STEPS TO REPRODUCE Disconnect and reconnect an external display. OBSERVED RESULT Laptop screen gets the task manager panel, external (HDMI) screen gets the original panel. EXPECTED RESULT Laptop screen gets the original panel, external (HDMI) screen gets the task manager panel. Operating System: Kubuntu 23.04 KDE Plasma Version: 5.27.4 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-20-generic (64-bit) Graphics Platform: X11 Processors: 8 × Intel® Core™ i5-8265U CPU @ 1.60GHz Memory: 15.3 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 Manufacturer: LENOVO Product Name: 20QD001UUS System Version: ThinkPad X1 Carbon 7th ADDITIONAL INFORMATION plasmashell version: 5.27.4 Kernel: Linux 6.2.0-20-generic #20-Ubuntu SMP PREEMPT_DYNAMIC Thu Apr 6 07:48:48 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 454356] Allow the user to switch off the drag and drop context menu
https://bugs.kde.org/show_bug.cgi?id=454356 advice2...@protonmail.com changed: What|Removed |Added CC||advice2...@protonmail.com --- Comment #1 from advice2...@protonmail.com --- I agree with this as well, this one is so important to me. KDE Plasma is amazing, this is literally one of the only things I can find that I do not care for, makes it very difficult to use. I am aware that you can use modifier keys to avoid them but for such a standard action should not really have to use a keyboard modifier to simple drag and drop a file with left mouse button. To me personally this is a pretty big deal, hopefully this could finally be addressed. There was a post requesting this from a long time ago (over 10 years ago) it had over 120 votes for it but unfortunately was never able to be fixed and I think the post was deleted? Nothing wrong with having these context menus be the default for those who like them, but seems odd that KDE, a group known for endless customization / settings, does not have an option to be able to turn these off / allow users to choose how drag & drops perform. I have never seen any other file managers use this approach with LMB D so with something that is far away from a standard, again seems odd not to be able to have a setting for something like this. I have however seen in Windows as well as some FM in Linux the use of the RMB D for these context menus which I would prefer. RMB makes more sense because a single click brings up context menu so D with RMB to bring up these CM would fit in better here. I will also add something not mentioned. This request is under the "Dolphin" category but it is a global issue throughout Plasma and all KDE products. I read in that old request post that apparently these context menus are coming from a file/library that all KDE products use. I have noticed them in Plasma, Dolphin and Krusader, even shows up in the Dolphin Flatpak. I posted a more in depth post about how this could possibly be handled here if anyone is interested https://discuss.kde.org/t/plasma-dolphin-drag-drop-context-menus/1809 Thank You Hopefully this one will be considered -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 470451] 3 feature requests for KAlarm: "today selector", "see past alarms", "defer presets"
https://bugs.kde.org/show_bug.cgi?id=470451 --- Comment #1 from David Jarvie --- Thanks for your suggestions. 1) Do you have any suggestions as to what form the "today" control could take, and where it should be positioned? 2) This would need some thought as to how desirable (i.e. to avoid confusion) or practical it is. 3) I think that choosing a few more or less arbitrary values for a preset list would be likely to only work for some users, and make others feel frustrated, so any preset list would need to be configurable by the user. While possible, it could take a significant amount of work to implement. -- You are receiving this mail because: You are watching all bug changes.
[okular] [Bug 470539] New: Screen corruption in any version starting from 22.07
https://bugs.kde.org/show_bug.cgi?id=470539 Bug ID: 470539 Summary: Screen corruption in any version starting from 22.07 Classification: Applications Product: okular Version: unspecified Platform: Compiled Sources OS: Linux Status: REPORTED Severity: major Priority: NOR Component: general Assignee: okular-de...@kde.org Reporter: wilfried.phil...@wphilips.eu Target Milestone: --- Created attachment 159401 --> https://bugs.kde.org/attachment.cgi?id=159401=edit screenshot showing screen corruption in scrollbar and dialog SUMMARY *** NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols. See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports *** STEPS TO REPRODUCE 1. on fedora36 or later install the most recent okular and start it 2. enable scrollbars 3. scrollbars are invisible (black on black) but work 4. open the configure okular dialog 5. the dialog appears but entries towards the bottom of the screen become increasingly garbled and unreadable OBSERVED RESULT screen corruption in dialog and in scrollbar region EXPECTED RESULT SOFTWARE/OS VERSIONS Linux + mate (fedora36,37 and 38) (available in About System) Qt Version: 5 (default fedora version) ADDITIONAL INFORMATION The corruption is caused by commit 41e59e4f55b2c092b45afe2d8541f8198d41b534 Set Qt::HighDpiScaleFactorRoundingPolicy::PassThrough also on Unix Reverting the commit everything works again with the current master. The comment of the commit claims to not see any adverse effect after 6 months, but this is an adverse effect. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 469757] kAlarm does not function if icon not present in system tray
https://bugs.kde.org/show_bug.cgi?id=469757 --- Comment #1 from David Jarvie --- Is KAlarm still running after removing it from the system tray? Bear in mind that if "Show in system tray" is selected, closing the main window will leave KAlarm running (in the system tray), but if "Show in system tray" is NOT selected, closing the main window will cause KAlarm to quit. So to keep using it while not showing it in the system tray, you have to leave it running in the same way as other applications, so if you're using a task manager in the panel, it will show there. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 470382] Baloo unable to index any files
https://bugs.kde.org/show_bug.cgi?id=470382 --- Comment #3 from Ovear --- Sorry for the typo. > Except that, is that possible to find what file / reason it wants to index > that caused those high memory demand? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 470382] Baloo unable to index any files
https://bugs.kde.org/show_bug.cgi?id=470382 Ovear changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Ovear --- Hi, Oh, change MemoryHigh works for me. According to status output from systemd, baloo just hits the memory limited by systemd. > Memory: 600.6M (high: 512.0M available: 0B) Is that possible to output a warning when baloo failed to request more memory as both systemd and baloo keep silence when it happened? Or may be adjust default memory limit is an option? I am not sure what is the optimal minimal required memory to keep Baloo from freezing. 512M may be a bit insufficient. But I also noticed Baloo doesn't seem to release memory after indexed. Except that, is possible to find what file / reason it wants to index that caused those high memory demand. > Memory: 8.1G (high: 31.2G available: 23.0G) Anyway, Thanks for your help. I will try to add this to Baloo's ArchWiki troubleshoot section. To those who may be affected by this, here is the process to increase systemd memory limit. 1. Use systemd edit function to override default limit > # systemctl --user edit kde-baloo 2. You may modify the file to something like below. ``` ### Anything between here and the comment below will become the contents of the drop-in file [Service] MemoryHigh=50% ### Edits below this comment will be discarded ``` 3. Restart kde-baloo, and it should work. > # systemctl restart --user kde-baloo -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 470477] Cannot create alarms
https://bugs.kde.org/show_bug.cgi?id=470477 --- Comment #3 from David Jarvie --- A possible fix is to right click on the alarm calendar in the calendar view panel, and ensure that "Use as default for active alarms" is selected. However, if the calendar is already selected as default, or if it still doesn't work after doing that, I suggest deleting and re-adding the alarm calendar as follows: 1) Select the active alarm calendar in the calendar view panel, and click Show Details. Note the File location. 2) Remove it from KAlarm's database by clicking Remove. (Note that this doesn't delete your actual alarm calendar file.) 3) Add the calendar again by clicking Add. In the dialog, enter the file location noted in step 1, select Active Alarms, enter "Active Alarms" as the name, and do not select read only. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470537] Dolphin crash when pressing del without selection file in selection mode
https://bugs.kde.org/show_bug.cgi?id=470537 Bug Janitor Service changed: What|Removed |Added Severity|normal |crash -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 470538] New: Possible file sorting issue in Plasma / Dolphin
https://bugs.kde.org/show_bug.cgi?id=470538 Bug ID: 470538 Summary: Possible file sorting issue in Plasma / Dolphin Classification: I don't know Product: kde Version: unspecified Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: advice2...@protonmail.com Target Milestone: --- SUMMARY Have noticed what I believe is a file sorting issue in Plasma / Dolphin. Happens when using " - " patterns which can be seen in examples below. When testing this out it seems like common practice by other Linux desktop environments as well as in Windows all seem to sort this way which is why I believe it could be viewed as an issue in Plasma / Dolphin. OBSERVED RESULT If filenames do not have an extension they will sort like the following… FRUIT FRUIT – Apple FRUIT – Grape which makes sense, does the same as "expected result" However in Plasma, if filenames include an extension, then they sort like the following… FRUIT – Apple.txt FRUIT – Grape.txt FRUIT.txt EXPECTED RESULT FRUIT.txt FRUIT – Apple.txt FRUIT – Grape.txt SOFTWARE/OS VERSIONS Linux/KDE Plasma: KDE Plasma Version: 5.20.5 KDE Frameworks Version: 5.78.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 420031] Status bar treats icons representing tags as folders
https://bugs.kde.org/show_bug.cgi?id=420031 logicalwillow changed: What|Removed |Added CC||robloka...@gmail.com -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 469676] Dolphin not opening when called with arguments
https://bugs.kde.org/show_bug.cgi?id=469676 Nicolas Fella changed: What|Removed |Added Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 469865] Crash when exporting scans to PDF
https://bugs.kde.org/show_bug.cgi?id=469865 John Doe changed: What|Removed |Added CC||kde.sp...@simplelogin.com --- Comment #5 from John Doe --- The console output basically tells you that the 'tesseract-data-eng' package is missing, you can install that to stop Skanpage from crashing. Though it shouldn't be necessary to have that if you are not scanning documents in English. -- You are receiving this mail because: You are watching all bug changes.
[Discover] [Bug 470325] Discover systray icon missing
https://bugs.kde.org/show_bug.cgi?id=470325 Dilam changed: What|Removed |Added CC||pasdabonneme...@gmail.com --- Comment #2 from Dilam --- More precisely, this bug is exactly the bug 469755 which is one of the issues caused by bug 425315. When I created bug 469755, I gave it a name more explicit than the current one. Something like "DiscoverNotifier icon not appearing in SystemTray". And someone has change it to "DiscoverNotifier can launch when SNI is not running" because the issue was more precisely about SNI not running at the time DiscoverNotifier is started by the OS, so that the icon does not appear in system tray. -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 470417] Skanpage crash when save multi page pdf
https://bugs.kde.org/show_bug.cgi?id=470417 John Doe changed: What|Removed |Added CC||kde.sp...@simplelogin.com Resolution|--- |DUPLICATE Status|REPORTED|RESOLVED --- Comment #1 from John Doe --- *** This bug has been marked as a duplicate of bug 469865 *** -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 469865] Crash when exporting scans to PDF
https://bugs.kde.org/show_bug.cgi?id=469865 John Doe changed: What|Removed |Added CC||danielesanna1...@gmail.com --- Comment #4 from John Doe --- *** Bug 470417 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[Skanpage] [Bug 469865] Crash when exporting scans to PDF
https://bugs.kde.org/show_bug.cgi?id=469865 Bug Janitor Service changed: What|Removed |Added Ever confirmed|0 |1 Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |ASSIGNED --- Comment #3 from Bug Janitor Service --- A possibly relevant merge request was started @ https://invent.kde.org/utilities/skanpage/-/merge_requests/50 -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 470382] Baloo unable to index any files
https://bugs.kde.org/show_bug.cgi?id=470382 tagwer...@innerjoin.org changed: What|Removed |Added Status|REPORTED|NEEDSINFO Resolution|--- |WAITINGFORINFO CC||tagwer...@innerjoin.org --- Comment #1 from tagwer...@innerjoin.org --- Can you perhaps check whether baloo is being throttled by its systemd service settings? There has been a recent change to these. Arch uses systemd, or at least Google thinks so, so try systemctl status --user kde-baloo and see if that comes up with anything strange. It should give you the config file, likely: /usr/lib/systemd/user/kde-baloo.service Check this and you will probably see a recently added line: MemoryHigh=512M This limits the amount of memory that baloo can grab. It could be that this is too tight, you'll see if you are up at the limit in the systemctl status (it will give you "high" and "available" values for memory). You can try changing the line to: MemoryHigh=50% and see if that makes any difference. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 470537] New: Dolphin crash when pressing del without selection file in selection mode
https://bugs.kde.org/show_bug.cgi?id=470537 Bug ID: 470537 Summary: Dolphin crash when pressing del without selection file in selection mode Classification: Applications Product: dolphin Version: 23.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Selection Mode Assignee: kfm-de...@kde.org Reporter: cylian.charbonnier+kdebugz...@gmail.com CC: felixer...@kde.org Target Milestone: --- SUMMARY STEPS TO REPRODUCE 1. open selection mode 2. press del SOFTWARE/OS VERSIONS Linux/KDE Plasma: 6.3.5-arch1-1 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 448310] Cursor sometimes slow after shutting lid
https://bugs.kde.org/show_bug.cgi?id=448310 --- Comment #6 from Eric Edlund --- My TouchPad is broken, sorry. -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 432546] SEP-MultiStar Broken; Loses Track of Guide Star
https://bugs.kde.org/show_bug.cgi?id=432546 John Evans changed: What|Removed |Added Resolution|--- |UNMAINTAINED Status|REPORTED|RESOLVED --- Comment #24 from John Evans --- email from Brett when I reached out to him on current status. Resolving issue based on this. Hi John, You won’t see any further details on my tickets because shortly thereafter I ended up migrating to NINA/PHD2. I was just struggling with software issues too frequently back then. My apologies for leaving the tickets hanging. If I recall correctly, the profile parameters in the guiding module that StellarSolver was using just did not work for my combination of equipment. This was worse on one 250mm FL scope with a ZWO 30mm guide cam, despite my best attempts at focusing. That was an extremely popular guide cam, but I did replace it with a William Optics Uniguide 32 and was amazed at the quality difference. Perhaps it was the source of most of these “lost star” issues, but I never went back to check with the newer UniGuide. If this issue is not being reported by others, I think you can probably safely close it. Thanks, Brett P.S. I’ve been following KStars development and it seems like it really picked up steam. There have been some great enhancements. While I’m likely sticking with NINA, there are still several awesome features that I miss from KStars/Ekos. Keep at it! -- You are receiving this mail because: You are watching all bug changes.
[valgrind] [Bug 470520] Multiple realloc zero errors crash in MC_(eq_Error)
https://bugs.kde.org/show_bug.cgi?id=470520 --- Comment #2 from Paul Floyd --- LGTM except that memcheck/tests/realloc_size_zero_again needs to be in .gitignore (and add this item to NEWS) -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 469590] Lag and doubled keystrokes when running SDDM in native Wayland mode with multiple screens and an NVIDIA GPU
https://bugs.kde.org/show_bug.cgi?id=469590 --- Comment #15 from Wilbur Jaywright --- Note, I am still having this problem with only one monitor, but it has been strictly of the kind where clicking on another user account icon clears it up. -- You are receiving this mail because: You are watching all bug changes.
[kalarm] [Bug 470477] Cannot create alarms
https://bugs.kde.org/show_bug.cgi?id=470477 --- Comment #2 from van.sny...@sbcglobal.net --- On Thu, 2023-06-01 at 14:36 +, David Jarvie wrote: > https://bugs.kde.org/show_bug.cgi?id=470477 > > --- Comment #1 from David Jarvie ---In the calendar > view (menu View -> Show Calendars), are any Active Alarmscalendars > shown? > If so, right click on the calendar and select Show Details. Please > report itsPermissions, Status and Default calendar setting. Today the "new" button and the "new" pick on the "file" menu are active. But when I try to create a display alarm, the response is "Failed to create alarm." The details are "Failed to append item." There is only one active alarm. Its permissions are read-write. The status is "Enabled." The Default is "No". These are independent of whether its box is checked. -- You are receiving this mail because: You are watching all bug changes.
[digikam] [Bug 469372] "Image cannot be loaded" – some images not rendered correctly
https://bugs.kde.org/show_bug.cgi?id=469372 --- Comment #24 from Maik Qualmann --- Bad news, Unicode support is broken in Exiv2-0.28. I can confirm it under Windows with file names that still worked under Exiv2-0.27.x. We don't notice it immediately, because from digiKam-8.0.0 onwards we read the metadata with ExifTool if there are problems in Exiv2. See bug report: https://github.com/Exiv2/exiv2/issues/2637 Maik -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 470536] New: Exiting in full screen mode saves awkward window placement
https://bugs.kde.org/show_bug.cgi?id=470536 Bug ID: 470536 Summary: Exiting in full screen mode saves awkward window placement Classification: Applications Product: konsole Version: 23.04.1 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: konsole-de...@kde.org Reporter: a...@signal11.com Target Milestone: --- SUMMARY This may be a bug in Kwin or a bug in Konsole, any assistance in getting it to the right place would be greatly appreciated! Full screen Konsole windows appear to save full screen geometry on exit, which means that at next launch an inconvenient window that has an offscreen title bar is restored by default, meaning a multistep process to move the window to get to the title bar and window controls to resize it. STEPS TO REPRODUCE 1. Open Konsole 2. F11 3. CTRL-M 4. Observe full screen terminal with no decorations visible 5. CTRL-D 6. Relaunch Konsole OBSERVED RESULT Observe new window that is full screen sized, but now has the title bar offscreen. EXPECTED RESULT At a minimum a new window that fits on the screen so the user can move it or resize it without too much fuss, maybe consider remembering full screen mode as well (where F11 would return to this window size). Either way, avoid creating new windows that have offscreen title bars under all circumstances. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: Arch 20230531 (available in About System) KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.106.0 Qt Version: 5.15.9 ADDITIONAL INFORMATION Wayland, multimonitor with external monitor above laptop monitor. -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 470299] Silent install no longer works
https://bugs.kde.org/show_bug.cgi?id=470299 michael changed: What|Removed |Added Status|REOPENED|ASSIGNED -- You are receiving this mail because: You are watching all bug changes.
[kdiff3] [Bug 470299] Silent install no longer works
https://bugs.kde.org/show_bug.cgi?id=470299 --- Comment #6 from michael --- Looks like I uploaded the wrong binary. Trying again. Going to keep this open until the fix can be confirmed. sha256: 89e0c4ffdffa7ec85ce8845f5909488df0998d80a8ca6cf77b1b1417993ca98e kdiff3-1.10.4-slientfixed-windows-x86_64.exe sha1: 1cb49f9c21e934a6f5c23a9f906137fb51d28862 kdiff3-1.10.4-slientfixed-windows-x86_64.exe The checksums are for the corrected installer. This will be replacing an existing file by the same name on the server. -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|crash |wishlist -- You are receiving this mail because: You are watching all bug changes.
[lattedock] [Bug 470114] Feature Request: Ways to better notify / manage / recover from crashed plasmoids or widgets
https://bugs.kde.org/show_bug.cgi?id=470114 Bug Janitor Service changed: What|Removed |Added Severity|wishlist|crash -- You are receiving this mail because: You are watching all bug changes.
[Spectacle] [Bug 470315] Resizing tall Spectacle window downward causes background to show above toolbar.
https://bugs.kde.org/show_bug.cgi?id=470315 --- Comment #6 from beedell.rokejulianlockhart --- Thanks. I'll move discussion to https://bugs.kde.org/show_bug.cgi?id=470535, then. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470535] noborderrule=2 doesn't work on Wayland, does on X.
https://bugs.kde.org/show_bug.cgi?id=470535 beedell.rokejulianlockhart changed: What|Removed |Added Attachment #159397|0 |1 is obsolete|| --- Comment #2 from beedell.rokejulianlockhart --- Created attachment 159399 --> https://bugs.kde.org/attachment.cgi?id=159399=edit kcmshell5 kcm_kwinrules A screenshot of the correct test configuration, per kcm_kwinrules's GUI. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470535] noborderrule=2 doesn't work on Wayland, does on X.
https://bugs.kde.org/show_bug.cgi?id=470535 --- Comment #1 from beedell.rokejulianlockhart --- Created attachment 159398 --> https://bugs.kde.org/attachment.cgi?id=159398=edit Test file. This is exactly what I've been using, which is why it contains a few more rules than necessary. Beware that KWin will replace any rulesets currently visible via kcmshell5 kcm_kwinrules if their names match those in the file provided – “X11” and/or “Wayland” – without prompt. That's a separate issue, though. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 466822] Window becomes blurry when dragged from toolbar or CSD in Wayland with Invert effect, or Wobbly Window effect enabled
https://bugs.kde.org/show_bug.cgi?id=466822 Thakshila Damsak changed: What|Removed |Added Status|RESOLVED|REOPENED Resolution|NOT A BUG |--- Ever confirmed|0 |1 --- Comment #11 from Thakshila Damsak --- Hey, I found that happens when both "Screen edge snap zone" and "Window snap zone" settings in Window Management --> Window Behaviour --> Movement are set to "none". Deleting the kwinrc file made them reset to the default setting. (default is 10px) So it fixed the problem. But changing them again to "none" causes the problem again. I got my preferred behavior by setting them to 1px. But I thought it would be a good idea to report this. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470535] New: noborderrule=2 doesn't work on Wayland, does on X.
https://bugs.kde.org/show_bug.cgi?id=470535 Bug ID: 470535 Summary: noborderrule=2 doesn't work on Wayland, does on X. Classification: Plasma Product: kwin Version: git-stable-Plasma/5.27 Platform: openSUSE OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: decorations Assignee: kwin-bugs-n...@kde.org Reporter: rokejulianlockh...@outlook.com Target Milestone: --- Created attachment 159397 --> https://bugs.kde.org/attachment.cgi?id=159397=edit .kwinrules SUMMARY If “No titlebar and frame” is set to Force No (noborderrule=2 in a .kwinrules file) on X, window borders are forced for every window except context menus. This is what I expect. On Wayland, all that this does is force the preference for XWayland windows. STEPS TO REPRODUCE 0. kcmshell5 kcm_kwinrules 1. “Add new...” 2. 0. Set “Window class (application)” to Unimportant. 2. 1. Set “Window types” to “All selected”. 2. 2. Apply. The consequence should be at least: wmclasscomplete=true noborderrule=2 OBSERVED RESULT Stated in SUMMARY. EXPECTED RESULT The same should occur in Wayland. SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20230529 KDE Plasma Version: 5.27.5 KDE Frameworks Version: 5.107.0 Qt Version: 5.15.9 Kernel Version: 6.3.4-1-default (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 3600 6-Core Processor Memory: 31.2 GiB of RAM Graphics Processor: AMD Radeon RX 5700 ADDITIONAL INFORMATION Weirdly, “Force”-ing the preference to Yes *does* work – it removes all window borders, even on Wayland. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 470334] Clipboard issue on Wayland - "Requested clipboard format is not available" in Libre Office
https://bugs.kde.org/show_bug.cgi?id=470334 --- Comment #5 from Michał Dybczak --- But what is the difference between Xorg and Wayland? On Xorg it works fine. This suggests an issue with XWayland side of things. I am not familiar with the topic, so I may ask a stupid question: is XWayland something general that various non-Wayland apps use to be displayed in Wayland correctly, or is it implemented individually per app? I ask this, because it may be issue with XWayland itself? -- You are receiving this mail because: You are watching all bug changes.
[kstars] [Bug 470534] Stars crash on Tools > Devices > List your Equipment
https://bugs.kde.org/show_bug.cgi?id=470534 Jasem Mutlaq changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution|--- |FIXED --- Comment #1 from Jasem Mutlaq --- This is already fixed in 3.6.5 branch but PPA update is pending. -- You are receiving this mail because: You are watching all bug changes.
