[kwin] [Bug 501828] Permanent focus stealing _or_ crash with non-sense Gtk4 code

2025-04-05 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501828 --- Comment #1 from postix --- If you click fast and often enough onto the "x" button in the titlebar of the sample app, you can make it close in the case of permanent focus stealing. -- You are receiving this mail because: You are watchi

[kwin] [Bug 501829] New: Permanent focus stealing with non-sense Gtk4 code

2025-04-05 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501829 Bug ID: 501829 Summary: Permanent focus stealing with non-sense Gtk4 code Classification: Plasma Product: kwin Version: 6.3.3 Platform: Other OS: Linux Status: REPORTE

[kwin] [Bug 501828] Crash with non-sense Gtk4 code

2025-04-04 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501828 postix changed: What|Removed |Added Summary|Permanent focus stealing|Crash with non-sense Gtk4 |_or_

[kwin] [Bug 501828] Permanent focus stealing _or_ crash with non-sense Gtk4 code

2025-04-04 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501828 --- Comment #3 from postix --- Backtrace of the crash: ``` #0 __pthread_kill_implementation (threadid=, signo=signo@entry=11, no_tid=no_tid@entry=0) at pthread_kill.c:44 #1 0x7f3e1dc9b453 in __pthread_kill_internal (threadid=, signo=11) at

[frameworks-kio] [Bug 500254] Full address in address bar not shown if hit ESC after clicking into the address bar to edit it

2025-04-04 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500254 postix changed: What|Removed |Added Status|CONFIRMED |RESOLVED Resolution

[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup

2025-03-30 Thread postix
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #91 from postix --- Has anyone tried to check with Hotspot [1], where the memory is being allocated over time in kwin_wayland to get a hint? [1] https://github.com/KDAB/hotspot -- You are receiving this mail because: You are watching all

[kwin] [Bug 496469] Memory leaks and instabilities on multi-monitor setup

2025-03-30 Thread postix
https://bugs.kde.org/show_bug.cgi?id=496469 --- Comment #92 from postix --- Sorry, I meant heaptrack: https://github.com/KDE/heaptrack -- You are receiving this mail because: You are watching all bug changes.

[gwenview] [Bug 485972] crash after invocation and upon close from krunner: QMimeProviderBase::isMimeTypeGlobsExcluded()

2025-03-26 Thread postix
https://bugs.kde.org/show_bug.cgi?id=485972 postix changed: What|Removed |Added Version|24.12.2 |24.12.3 -- You are receiving this mail because: You

[gwenview] [Bug 485972] crash after invocation and upon close from krunner: QMimeProviderBase::isMimeTypeGlobsExcluded()

2025-03-26 Thread postix
https://bugs.kde.org/show_bug.cgi?id=485972 --- Comment #4 from postix --- ^ Edit: Mount the folder *of* a memory card, not *on*. The folder is automatically mounted at /media/... (Sorry, edits are still not possible in bugzilla ...) -- You are receiving this mail because: You are watching

[gwenview] [Bug 485972] crash after invocation and upon close from krunner: QMimeProviderBase::isMimeTypeGlobsExcluded()

2025-03-26 Thread postix
https://bugs.kde.org/show_bug.cgi?id=485972 --- Comment #3 from postix --- Steps to reproduce it reliably for me: 1) Mount a folder on a memory card of a camera 2) Open a folder with (up to 5k) JPEGs in Dolphin 3) Open a JPEG in Gwenview (by double clicking in Dolphin) 4) Close Gwenview

[plasmashell] [Bug 500927] Only one item shows up in the clipboard history, irrespective of configured history size

2025-03-22 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500927 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail

[plasmashell] [Bug 498341] Clipboard text is sometimes non-pasteable

2025-03-22 Thread postix
https://bugs.kde.org/show_bug.cgi?id=498341 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail

[frameworks-kio] [Bug 501581] New address bar: Different widths depending on the path

2025-03-21 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501581 --- Comment #2 from postix --- > Didn't the old one do this too? Might have been the case, unfortunately I can't easily go back now to check. :) (In reply to Nate Graham from comment #1) > The URL bar has some very complicated

[frameworks-kio] [Bug 501667] URL/Location bar truncates path when exiting edit mode with Escape key

2025-03-21 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501667 postix changed: What|Removed |Added CC||pos...@posteo.eu --- Comment #5 from postix

[frameworks-kio] [Bug 501587] Folder icon is clickable even if there are no subfolders

2025-03-21 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501587 postix changed: What|Removed |Added Summary|New address bar: Folder |Folder icon is clickable |icon is

[kwin] [Bug 501828] Crash with non-sense Gtk4 code

2025-03-21 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501828 --- Comment #4 from postix --- I've split the two issues and created another one for the focus stealing: #501829. So this one here is only about Kwin crashing now. -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 501828] Permanent focus stealing _or_ crash with non-sense Gtk4 code

2025-03-21 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501828 --- Comment #2 from postix --- You can also click into into another app, e.g. Konsole, until eventually Konsole will gain focus. The main window will hide behind Konsole, but the popover keeps staying on top of all windows. -- You are receiving this

[kwin] [Bug 501828] New: Permanent focus stealing _or_ crash with non-sense Gtk4 code

2025-03-21 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501828 Bug ID: 501828 Summary: Permanent focus stealing _or_ crash with non-sense Gtk4 code Classification: Plasma Product: kwin Version: 6.3.3 Platform: Other OS: Li

[kmenuedit] [Bug 501739] Improve UX if text is too long for the input fields

2025-03-19 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501739 --- Comment #2 from postix --- Make sense. Got a last idea: #3 Show a popup multi-line input field on click above or below the input field When the text fits (does not fit), popup closes (opens) and the focus is set accordingly to the right control

[frameworks-kio] [Bug 501737] New: Make the address drag-able if the whole path doesn't fit into the view

2025-03-19 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501737 Bug ID: 501737 Summary: Make the address drag-able if the whole path doesn't fit into the view Classification: Frameworks and Libraries Product: frameworks-kio Version: 6.12.0

[frameworks-kio] [Bug 501587] New address bar: Folder icon is clickable even if there are no subfolders

2025-03-19 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501587 postix changed: What|Removed |Added Component|general |URL navigator -- You are receiving this mail because

[frameworks-kio] [Bug 501577] New address bar: Text overflows when Dolphin's window is very narrow

2025-03-19 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501577 postix changed: What|Removed |Added Component|general |URL navigator -- You are receiving this mail because

[frameworks-kio] [Bug 501579] Impossible to edit the address bar when the window is very small

2025-03-19 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501579 postix changed: What|Removed |Added Component|general |URL navigator -- You are receiving this mail because

[frameworks-kio] [Bug 501582] New address bar: Path separator can flicker when switching tabs

2025-03-19 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501582 postix changed: What|Removed |Added Component|general |URL navigator -- You are receiving this mail because

[kmenuedit] [Bug 501739] New: Improve UX if text is too long for the input fields

2025-03-19 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501739 Bug ID: 501739 Summary: Improve UX if text is too long for the input fields Classification: Applications Product: kmenuedit Version: 6.3.3 Platform: Other OS: Linux St

[frameworks-kio] [Bug 501575] New address bar: Clicking on the last folder icon in the hierarchy makes it jump a few pixels to the left

2025-03-19 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501575 postix changed: What|Removed |Added Component|general |URL navigator -- You are receiving this mail because

[frameworks-kio] [Bug 501581] New address bar: Different widths depending on the path

2025-03-19 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501581 postix changed: What|Removed |Added Component|general |URL navigator -- You are receiving this mail because

[frameworks-kio] [Bug 501589] New address bar: | separators are sometimes thin or bold, also depends on address bar's width

2025-03-19 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501589 postix changed: What|Removed |Added Component|general |URL navigator -- You are receiving this mail because

[kwin] [Bug 501580] Tile to left or right: Can resize the window only up to 80% of the screen's size horizontally

2025-03-17 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501580 postix changed: What|Removed |Added Status|NEEDSINFO |RESOLVED Resolution|WAITINGFORINFO

[dolphin] [Bug 475106] Raise the address bar to better indicate that it's clickable

2025-03-16 Thread postix
https://bugs.kde.org/show_bug.cgi?id=475106 --- Comment #6 from postix --- I haven't installed the update for my parents yet, so I can't tell if it works better for them, but I've started been trying it out myself now: Besides minor issue, it works quiet fine overall. I do thin

[frameworks-kio] [Bug 501589] New address bar: | separators are sometimes thin or bold, also depends on address bar's width

2025-03-16 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501589 --- Comment #1 from postix --- I've checked another system with 150% scaling: there are several bold and thin ones for the same path. Looks a bit odd. -- You are receiving this mail because: You are watching all bug changes.

[frameworks-kio] [Bug 501589] New address bar: | separators are sometimes thin or bold, also depends on address bar's width

2025-03-16 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501589 postix changed: What|Removed |Added Summary|New address bar: Different |New address bar: | |widths of the

[frameworks-kio] [Bug 501589] New: New address bar: Different widths of the | separators when changing the address bar's size

2025-03-16 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501589 Bug ID: 501589 Summary: New address bar: Different widths of the | separators when changing the address bar's size Classification: Frameworks and Libraries Product: frameworks-kio Versi

[frameworks-kio] [Bug 501587] New address bar: Folder icon is clickable even if there are no subfolders

2025-03-16 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501587 --- Comment #1 from postix --- The same also happens if you delete all subfolder in the terminal or in 2nd Dolphin window, but those cases I would say are very edge-like. The one above with the last folder containing no subfolders is likely rather

[frameworks-kio] [Bug 501587] New: New address bar: Folder icon is clickable even if there are no subfolders

2025-03-16 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501587 Bug ID: 501587 Summary: New address bar: Folder icon is clickable even if there are no subfolders Classification: Frameworks and Libraries Product: frameworks-kio Version: 6.12.0

[frameworks-kio] [Bug 501582] New: New address bar: Path separator can flicker when switching tabs

2025-03-16 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501582 Bug ID: 501582 Summary: New address bar: Path separator can flicker when switching tabs Classification: Frameworks and Libraries Product: frameworks-kio Version: 6.12.0 Platfo

[frameworks-kio] [Bug 501581] New: New address bar: Different widths depending on the path

2025-03-16 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501581 Bug ID: 501581 Summary: New address bar: Different widths depending on the path Classification: Frameworks and Libraries Product: frameworks-kio Version: 6.12.0 Platform: Othe

[kwin] [Bug 501580] New: Tile to left or right: Can resize the window only up to 80% of the screen's size horizontally

2025-03-16 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501580 Bug ID: 501580 Summary: Tile to left or right: Can resize the window only up to 80% of the screen's size horizontally Classification: Plasma Product: kwin Version: 6.3.3 Platf

[frameworks-kio] [Bug 501579] Impossible to edit the address bar when the window is very small

2025-03-16 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501579 --- Comment #2 from postix --- Created attachment 179458 --> https://bugs.kde.org/attachment.cgi?id=179458&action=edit Screenshot: same issue with the hint when clicking the "v" chevron -- You are receiving this mail because: You

[frameworks-kio] [Bug 501579] Impossible to edit the address bar when the window is very small

2025-03-16 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501579 postix changed: What|Removed |Added Keywords||usability -- You are receiving this mail because

[frameworks-kio] [Bug 501579] Impossible to edit the address bar when the window is very small

2025-03-16 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501579 --- Comment #1 from postix --- Created attachment 179457 --> https://bugs.kde.org/attachment.cgi?id=179457&action=edit Screenshot -- You are receiving this mail because: You are watching all bug changes.

[frameworks-kio] [Bug 501579] New: Impossible to edit the address bar when the window is very small

2025-03-16 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501579 Bug ID: 501579 Summary: Impossible to edit the address bar when the window is very small Classification: Frameworks and Libraries Product: frameworks-kio Version: 6.12.0 Platf

[frameworks-kio] [Bug 501577] New: New address bar: Text overflows when Dolphin's window is very narrow

2025-03-16 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501577 Bug ID: 501577 Summary: New address bar: Text overflows when Dolphin's window is very narrow Classification: Frameworks and Libraries Product: frameworks-kio Version: 6.12.0 P

[frameworks-kio] [Bug 501575] New: New address bar: Clicking on the last folder icon in the hierarchy makes it jump a few pixels to the left

2025-03-16 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501575 Bug ID: 501575 Summary: New address bar: Clicking on the last folder icon in the hierarchy makes it jump a few pixels to the left Classification: Frameworks and Libraries Product: frameworks-kio

[plasmashell] [Bug 501309] Need to scroll for the relevant search result: Better strategy for search result's view needed

2025-03-15 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501309 postix changed: What|Removed |Added Keywords||usability -- You are receiving this mail because

[plasmashell] [Bug 500203] Pasting Unicode text in clipboard history that was previously copied from Firefox would output incorrect characters

2025-03-15 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500203 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail

[Spectacle] [Bug 446628] Spectacle: Screenshot request failed: "The process is not authorized to take a screenshot" when desktop files exists in user directory

2025-03-14 Thread postix
https://bugs.kde.org/show_bug.cgi?id=446628 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail

[plasmashell] [Bug 501466] plasmashell crashed in QQuickItemPrivate::addToDirtyList() when waking displays after login

2025-03-13 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501466 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail

[kwin] [Bug 500455] Display freezes upon opening fullscreen views if both HDR and "Prefer color accuracy" are enabled

2025-03-11 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500455 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail

[plasmashell] [Bug 501309] New: Need to scroll for the relevant search result: Better strategy for search result's view needed

2025-03-10 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501309 Bug ID: 501309 Summary: Need to scroll for the relevant search result: Better strategy for search result's view needed Classification: Plasma Product: plasmashell Version: 6.3.2

[plasmashell] [Bug 501309] Need to scroll for the relevant search result: Better strategy for search result's view needed

2025-03-10 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501309 postix changed: What|Removed |Added Status|REPORTED|RESOLVED Resolution

[dolphin] [Bug 501269] New: Segfault on closing Dolphin

2025-03-09 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501269 Bug ID: 501269 Summary: Segfault on closing Dolphin Classification: Applications Product: dolphin Version: 24.12.3 Platform: Other OS: Linux Status: REPORTED

[plasmashell] [Bug 499834] Plasmashell frequently crashes in QWindow::screen

2025-03-08 Thread postix
https://bugs.kde.org/show_bug.cgi?id=499834 postix changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=499383

[plasmashell] [Bug 499383] plasma crashed in QtWaylandClient::QWaylandWindow::handleScreensChanged

2025-03-08 Thread postix
https://bugs.kde.org/show_bug.cgi?id=499383 postix changed: What|Removed |Added CC||pos...@posteo.eu See Also|https

[plasmashell] [Bug 477939] On Wayland, having multiple panels sharing the same edge cause notifications and widgets to not touch their edge

2025-03-08 Thread postix
https://bugs.kde.org/show_bug.cgi?id=477939 postix changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=500668

[plasmashell] [Bug 500668] Notification position offset by combined thickness of all panels on screen edge, not just the one with the Notifications widget on it

2025-03-08 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500668 postix changed: What|Removed |Added See Also|https://bugs.kde.org/show_b | |ug.cgi?id=477939

[plasmashell] [Bug 498593] Laptop goes into (broken) standby, if lid is closed during shut down

2025-03-07 Thread postix
https://bugs.kde.org/show_bug.cgi?id=498593 --- Comment #7 from postix --- Thanks Yifan Zhu! Nate, could we maybe reopen this until it's clarified that it's definitely not a Plasma bug and not a lucky coincidence with the HP laptop, so that this bug gets more attention? Who of us a

[kwin] [Bug 501139] multigpu offloading doesn't work when nvidia is the primary display aka reverse prime

2025-03-06 Thread postix
https://bugs.kde.org/show_bug.cgi?id=501139 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail

[plasmashell] [Bug 500478] Screen locker sometimes only shows black screen after unlocking with password when fingerprint reader is available

2025-03-06 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500478 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail

[dolphin] [Bug 475106] Raise the address bar to better indicate that it's clickable

2025-03-03 Thread postix
https://bugs.kde.org/show_bug.cgi?id=475106 --- Comment #5 from postix --- (In reply to Nate Graham from comment #4) > Effectively done by that commit. It's great! <3 Thanks so much! -- You are receiving this mail because: You are watching all bug changes.

[gwenview] [Bug 485972] crash after invocation and upon close from krunner: QMimeProviderBase::isMimeTypeGlobsExcluded()

2025-03-03 Thread postix
https://bugs.kde.org/show_bug.cgi?id=485972 --- Comment #2 from postix --- ^ However, I have not used krunner and cannot provide any steps to reproduce. -- You are receiving this mail because: You are watching all bug changes.

[gwenview] [Bug 485972] crash after invocation and upon close from krunner: QMimeProviderBase::isMimeTypeGlobsExcluded()

2025-03-03 Thread postix
https://bugs.kde.org/show_bug.cgi?id=485972 postix changed: What|Removed |Added Version|24.02.2 |24.12.2 Status|REPORTED

[dolphin] [Bug 500147] Dolphin crashed on closing somwhere around KFilePlacesItem::~KFilePlacesItem KBookmark::~KBookmark

2025-03-03 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500147 postix changed: What|Removed |Added Platform|Other |Fedora RPMs --- Comment #8 from postix --- Currently

[kremotecontrol] [Bug 500767] Rebinding buttons breaks connection even KCM is closed

2025-03-01 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500767 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-27 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #54 from postix --- > This disables by default, I'm not sure that implies the setting can be > overridden (and where). I've not been successful here. Me neither. https://doc.opensuse.org/documentation/leap/archive/15.2/

[kwin] [Bug 500666] Custom Tiling directional keyboard shortcuts don't work properly when display scaling is set to anything other than 100%

2025-02-27 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500666 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail

[kdenlive] [Bug 499221] User Story: User-Definable Starting Timecode for Edit Sequences in Kdenlive

2025-02-27 Thread postix
https://bugs.kde.org/show_bug.cgi?id=499221 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail

[systemsettings] [Bug 472954] "Pause indexer" button does not work when clicked while baloo indexes files

2025-02-26 Thread postix
https://bugs.kde.org/show_bug.cgi?id=472954 --- Comment #9 from postix --- Have you checked if the kde-baloo.service is running? > systemctl --user status kde-baloo I've noticed that the issue seems to be gone for me, since I've managed to control baloo by systemd. -- You are r

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-26 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #50 from postix --- systemd-analyze --user log-level debug I see in journalctl > Failed to establish memory pressure event source, ignoring: Operation not > supported > Failed to connect to /run/systemd/oom/io.systemd.ManagedOOM

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-26 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #49 from postix --- * balooctl status claims "Indexer state: Indexing file content", while it should only be indexing file names, as this is set both in the baloofilerc and in the kcm. Likely this error comes from the fact that

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-26 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #48 from postix --- (In reply to tagwerk19 from comment #46) > That's a lot of information to sort through... > That's a lot of information to sort through... Unfortunately posting larger sequential updates on Bugzilla

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #40 from postix --- ``` balooctl config show contentIndexing no ``` contradicting balooctl status -- You are receiving this mail because: You are watching all bug changes.

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #44 from postix --- So, I let the system run and index for an hour: it uses now 8.3 GB RES RAM and 100% CPU, the fan is spinning, but in the moment it lags much less. Not sure if I should call it resolved as it had lagged shortly after

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #43 from postix --- > The high cpu/ram usage stays but the system seems to feel snappier now. > Unfortunately it's hard to objectively benchmark. but definitely not as snappy as when baloo_file_extractor is not running. It s

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #42 from postix --- I've noticed that the ntfs3 driver was blacklisted, I've loaded it now with modprob and remounted the drives: The high cpu/ram usage stays but the system seems to feel snappier now. Unfortunately it

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #41 from postix --- `systemctl --user stop kde-baloo.service` has stopped baloo_file and baloo_file_indexer immediately at least now. :) -- You are receiving this mail because: You are watching all bug changes.

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #39 from postix --- ``` balooctl indexSize File Size: 57.46 GiB Used: 2.66 GiB PostingDB: 3.72 GiB 140.075 % PositionDB: 302.12 MiB11.099 % DocTerms

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #38 from postix --- After running 1h 22 minutes and having baloo monitor opened ever since it shows me * 40 lines in total, out of those * 25 starting with Indexing: /media/foo/$fileXYZ :Ok * 15 just ": Ok" What do these ":

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #37 from postix --- This looks actually fine to me: ``` cat ~/.config/baloofilerc [Basic Settings] Indexing-Enabled=true [General] dbVersion=2 exclude filters=*~,*.part,*.o,*.la,*.lo,*.loT,*.moc,moc_*.cpp,qrc_*.cpp,ui_*.h

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #36 from postix --- On Fedora 41 I see the Memory: line in status, while here on openSUSE Tumbleweed I see it not, though the service file contains an entry: ``` cat /usr/lib/systemd/user/kde-baloo.service [Unit] Description=Baloo File

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #35 from postix --- Interestingly > balooctl status Baloo File Indexer is running Indexer state: Indexing file content Total files indexed: 4,266,801 Files waiting for content indexing: 1,087,769 Files failed to index: 0 Current size

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #34 from postix --- 26 minutes after starting the indexing I see > baloo_file[2519]: kf.baloo: KDE Baloo File Indexer has reached the inotify > folder watch limit. File changes will be ignored. in the systemd service status ``` ba

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #33 from postix --- > I see 8 lines with Sorry that I can't edit posts here. 8 lines corresponding to different files. -- You are receiving this mail because: You are watching all bug changes.

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #32 from postix --- > /usr/libexec/baloo_file_extractor has come up now and is visible in sytemd status I see 8 lines with > baloo_file_extractor[3629]: Invalid encoding. Ignoring "/media/foo/bar/" balooctl status Baloo

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #31 from postix --- So I've changed the entry in baloofilerc to meet the systemd script start condition, enabled the service and rebooted: ``` > systemctl --user status kde-baloo.service ● kde-baloo.service - Baloo File Indexe

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #30 from postix --- > Is Baloo actually running? If it is, it is running outside of the systemd > limits. I've had disabled baloo with `balooctl disable`, rebooted, checked > ~/.config/baloofilerc it says > Indexing-En

[dolphin] [Bug 500147] Dolphin crashed on closing somwhere around KFilePlacesItem::~KFilePlacesItem KBookmark::~KBookmark

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500147 --- Comment #6 from postix --- Yeah just happened again, now w/o any mount. Just opened Dolphin and closed it. -- You are receiving this mail because: You are watching all bug changes.

[kwin] [Bug 470789] Firefox flickers in Plasma Wayland session

2025-02-25 Thread postix
https://bugs.kde.org/show_bug.cgi?id=470789 postix changed: What|Removed |Added Resolution|--- |WAITINGFORINFO CC

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-24 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #27 from postix --- ``` > systemctl --user status kde-baloo.service ○ kde-baloo.service - Baloo File Indexer Daemon Loaded: loaded (/usr/lib/systemd/user/kde-baloo.service; disabled; preset: disabled) Active: inactive (d

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-24 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #26 from postix --- > Are you using the Paragon NTFS drivers or the older FUSE ntfs-3g drivers? mount says /dev/sda1 on /media/foo type fuseblk (rw,nosuid,nodev,relatime,user_id=0,group_id=0,allow_other,blksize=4096) /dev/sdb1 on /me

[Spectacle] [Bug 469402] Cannot take screenshot after taking a recording

2025-02-24 Thread postix
https://bugs.kde.org/show_bug.cgi?id=469402 postix changed: What|Removed |Added CC||pos...@posteo.eu -- You are receiving this mail

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-24 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #24 from postix --- I've changed the setting to indexing filenames only. Same picture. In htop one can observe a constant switching between the process state's R(unning) and D(isk Sleep). -- You are receiving this mail becaus

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-24 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #13 from postix --- Created attachment 178820 --> https://bugs.kde.org/attachment.cgi?id=178820&action=edit Screenshot of heaptrack summary: Recorded 25 min from start I've started the recording right after baloo_file_extra

[Spectacle] [Bug 489190] Spectacle and KDE 6.1 (fake) session restore interaction

2025-02-24 Thread postix
https://bugs.kde.org/show_bug.cgi?id=489190 postix changed: What|Removed |Added CC||pos...@posteo.eu --- Comment #2 from postix --- On

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-24 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #20 from postix --- Created attachment 178826 --> https://bugs.kde.org/attachment.cgi?id=178826&action=edit heaptrack: allocations over time (25 min recording) -- You are receiving this mail because: You are watching all bug changes.

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-24 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #18 from postix --- I don't understand why there's anything swapped after all while the system has sufficient memory left. Swap is currently 3.8 GB, peak RSS was 4.2 GB, the system has 32 GB installed. -- You are receiving

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-24 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #17 from postix --- Created attachment 178824 --> https://bugs.kde.org/attachment.cgi?id=178824&action=edit Screenshot of heaptrack bottom up memory leak 2/2: Recorded over 25 mins from start -- You are receiving this mail becau

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-24 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #22 from postix --- Created attachment 178828 --> https://bugs.kde.org/attachment.cgi?id=178828&action=edit heaptrack: req allocation sizes (25 min recording) -- You are receiving this mail because: You are watching all bug changes.

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-24 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 postix changed: What|Removed |Added Attachment #178827|0 |1 is obsolete

[frameworks-baloo] [Bug 500665] Baloo File Extractor uses 25-40% CPU and 3 GB of RAM while indexing an HDD and slows down the whole system

2025-02-24 Thread postix
https://bugs.kde.org/show_bug.cgi?id=500665 --- Comment #21 from postix --- Created attachment 178827 --> https://bugs.kde.org/attachment.cgi?id=178827&action=edit heaptrack: temp allocations over time (25 min recording) -- You are receiving this mail because: You are watching

  1   2   3   4   5   6   7   8   9   10   >