[kwin] [Bug 465937] New: Resizing quick tiled windows affects quick tiling behavior
https://bugs.kde.org/show_bug.cgi?id=465937 Bug ID: 465937 Summary: Resizing quick tiled windows affects quick tiling behavior Classification: Plasma Product: kwin Version: 5.27.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Quick Tiling Assignee: kwin-bugs-n...@kde.org Reporter: r...@rekurs.io Target Milestone: --- SUMMARY Resizing a quick tiled window will change how windows are tiled until kwin is restarted. STEPS TO REPRODUCE 1. Quick tile a window to the left so it takes one half of the screen. 2. Resize it horizontally to a quarter of the screen. 3. Now all windows quick tiled to the left will take one quarter instead of half of the screen. Windows tiled to the right will take 3/4. EXPECTED RESULT The "layout" should not preserved. Quick tiled windows used to always take half of the screen (or a quarter in corners). SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465937] Resizing quick tiled windows affects quick tiling behavior
https://bugs.kde.org/show_bug.cgi?id=465937 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 465489] Can no longer unassign "space" from activating selection mode
https://bugs.kde.org/show_bug.cgi?id=465489 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465937] Resizing quick tiled windows affects quick tiling behavior
https://bugs.kde.org/show_bug.cgi?id=465937 --- Comment #2 from Riku --- Created attachment 156405 --> https://bugs.kde.org/attachment.cgi?id=156405&action=edit Demonstration of the issue I've added a video where you can see the issue. I tile to the left (super+left), horizontal resize (super+right click), and now I'm stuck with these strange sizes on all subsequent quick tiles to the left and right, including after closing the window and opening a new one. I forgot to include it in the recording but like I mentioned, regular behavior can be restored by running "kwin_x11 --replace". Also of note, I temporarily moved my .cache, .config and .local to make sure it's not some broken config issue. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466050] New: Triggering selection mode by accident
https://bugs.kde.org/show_bug.cgi?id=466050 Bug ID: 466050 Summary: Triggering selection mode by accident Classification: Applications Product: dolphin Version: 22.12.2 Platform: Other OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: Selection Mode Assignee: kfm-de...@kde.org Reporter: r...@rekurs.io CC: felixer...@kde.org Target Milestone: --- SUMMARY While I'm sure this feature is great for touchscreen users, as a heavy keyboard user I find myself triggering selection mode exclusively by accident. The thing is, why would I ever want to use selection mode if I'm not limited to touch controls? On a keyboard it's more or less worthless and even with a mouse, ctrl/shift + left click and right click for actions works fine. Some possible solutions come to mind. A. Add an option to fully disable selection mode. B. Do not trigger selection mode with keyboard. It could still be triggered with mouse or touch. C. Put selection mode on some shortcut that won't be constantly hit by accident. SOFTWARE/OS VERSIONS Linux/KDE Plasma: Arch Linux KDE Plasma Version: 5.27.0 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466050] Triggering selection mode by accident
https://bugs.kde.org/show_bug.cgi?id=466050 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 457565] Multiscreen: Window's shadow and outline bleed over when window is maximized or tiled to an edge adjacent to another screen
https://bugs.kde.org/show_bug.cgi?id=457565 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466050] Triggering selection mode by accident
https://bugs.kde.org/show_bug.cgi?id=466050 --- Comment #2 from Riku --- File manager GUIs have worked more or less the same for as long as I can remember and now suddenly the muscle memory is destroyed. But I won't argue against accessibility and it's great that people are actually thinking about this stuff. It's just that it seems to always come at the expense of irritating proficient users. >Which keyboard shortcut are you triggering by accident? Mostly the Space key >shortcut or others as well? Mostly space indeed. I noticed there was already some discussion about allowing rebinding space which would help a lot! However I do also end up hitting copy or cut on an empty selection. Say I try to copy but the file I thought was selected isn't. Now I would instinctively try space, which actually exits selection mode. Even with the original behavior of space restored, entering selection mode on an empty copy is not what I wanted and doesn't help me in terms number of key presses, etc. I just don't see myself ever benefitting from selection mode, only having to cancel it after having mistakenly activated it. I'd like to hear your thoughts on my proposed solutions. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 465937] Resizing quick tiled windows affects quick tiling behavior
https://bugs.kde.org/show_bug.cgi?id=465937 --- Comment #4 from Riku --- Closing the tiled windows and the state persisting just doesn't make any sense. I think on windows 10 for example, you can do something similar where windows snapped to the sides fill the remaining space, but new windows snapped on an empty desktop still take half. Why would anyone want to preserve the invisible layout that cannot be reset? Wouldn't the people who want persistent tiling layouts be using the new custom tiling thing anyway? -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466050] Triggering selection mode by accident
https://bugs.kde.org/show_bug.cgi?id=466050 --- Comment #4 from Riku --- Dashon, regarding space specifically there's a related report here https://bugs.kde.org/show_bug.cgi?id=465489 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 461897] Mouse Pointer leaves duplicate on second monitor when moving quickly between monitors
https://bugs.kde.org/show_bug.cgi?id=461897 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 466050] Triggering selection mode by accident
https://bugs.kde.org/show_bug.cgi?id=466050 --- Comment #7 from Riku --- Entering selection mode on actions like copy just seems redundant to be honest. But admittedly, copying on an empty selection is not that regular of an occurrance and maybe I could learn to live with how it works once space is fixed. While this isn't ideal for me personally, I don't see a good solution right now. I (reluctantly) agree to mark as duplicate. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 428272] Unmaximize does not restore window size/position correctly if KWin's Quicktile shortcuts were used before
https://bugs.kde.org/show_bug.cgi?id=428272 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 468127] New: Window title in tabbox is not updated until active window changes
https://bugs.kde.org/show_bug.cgi?id=468127 Bug ID: 468127 Summary: Window title in tabbox is not updated until active window changes Classification: Plasma Product: kwin Version: 5.27.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: tabbox Assignee: kwin-bugs-n...@kde.org Reporter: r...@rekurs.io Target Milestone: --- Created attachment 157825 --> https://bugs.kde.org/attachment.cgi?id=157825&action=edit Demonstration of the issue SUMMARY Switching tabs in a window doesn't update the window title in the tabbox. This seems to happen with any tabbed program. STEPS TO REPRODUCE 1. Change tab in a window. 2. Hold alt+tab and observe incorrect window title. SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 5.27.3 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.8 -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 464225] copy/move symbolic link moves link destination instead
https://bugs.kde.org/show_bug.cgi?id=464225 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 488110] Last Active Screen and Open Window Under Mouse Cover Seem to Be Clashing
https://bugs.kde.org/show_bug.cgi?id=488110 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487392] Item selection doesn't reset x or y properly between mouse click and arrow keys
https://bugs.kde.org/show_bug.cgi?id=487392 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477086] MPV not able to enter fullscreen mode and FS apps don't trigger the compositor to suspend/undredir X11
https://bugs.kde.org/show_bug.cgi?id=477086 Riku changed: What|Removed |Added CC||r...@rekurs.io Status|RESOLVED|REOPENED Resolution|WORKSFORME |--- --- Comment #17 from Riku --- I'm still experiencing this on kwin 6.0.1. Looks like mpv can't go fullscreen if the video aspect ratio is not the same as the monitor. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 477086] MPV not able to enter fullscreen mode and FS apps don't trigger the compositor to suspend/undredir X11
https://bugs.kde.org/show_bug.cgi?id=477086 --- Comment #19 from Riku --- (In reply to Vlad Zahorodnii from comment #18) > Can you add a window rule "obey geometry restrictions" that forces "No" for > mpv? Having set the rule mpv now behaves as expected. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 480494] Dolphin Panels Change When Rapidly Minimizing and Maximizing Program
https://bugs.kde.org/show_bug.cgi?id=480494 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 477201] Wayland: Right click and dragging does not activate context menu item (no menu rolling)
https://bugs.kde.org/show_bug.cgi?id=477201 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482129] New: Windows won't take focus on wayland
https://bugs.kde.org/show_bug.cgi?id=482129 Bug ID: 482129 Summary: Windows won't take focus on wayland Classification: Plasma Product: kwin Version: unspecified Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: r...@rekurs.io Target Milestone: --- SUMMARY On wayland, some programs won't take focus if they were already running. This happens a lot with programs bound to shortcuts or opening files for example. STEPS TO REPRODUCE Run systemsettings and minimize it, then run systemsettings again. The window isn't raised. It does get highlighted on the taskbar though. SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 ADDITIONAL INFORMATION Kwin version: 6.0.0 (wasn't listed in the form) -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482130] New: Text is misaligned when renaming a file inline in dolphin icon view
https://bugs.kde.org/show_bug.cgi?id=482130 Bug ID: 482130 Summary: Text is misaligned when renaming a file inline in dolphin icon view Classification: Applications Product: dolphin Version: 24.02.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: view-engine: icons mode Assignee: dolphin-bugs-n...@kde.org Reporter: r...@rekurs.io CC: kfm-de...@kde.org Target Milestone: --- SUMMARY When renaming a file inline in icon view the text shifts left. STEPS TO REPRODUCE While using icon view, use inline rename and type or delete something. The text will shift left. SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 6.0.0 KDE Frameworks Version: 6.0.0 Qt Version: 6.6.2 -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 482129] Windows won't take focus on wayland
https://bugs.kde.org/show_bug.cgi?id=482129 --- Comment #2 from Riku --- (In reply to Vlad Zahorodnii from comment #1) > Something to look into later. Hopefully not too much later? While this has been more or less the only major issue I've ran into with plasma 6 on wayland it is extremely frustrating. So, kwin sees an application wants focus but won't actually do anything because you didn't ask nicely? Is this just yet another case of wayland being stupid and user hostile? And to be clear this is not limited to konsole. It seems to happen with most programs that can only have a single "instance", regardless of how they're launched. I have programs bound to global shortcuts like qalculate or sublime text, just to name a few. I noticed Bug 479491 also describes a similar problem. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 482834] Middle-clicking a file in dolphin opens with second application for the file mime, breaking default selection operation
https://bugs.kde.org/show_bug.cgi?id=482834 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 475575] New: Underscores display as spaces in the window title bar
https://bugs.kde.org/show_bug.cgi?id=475575 Bug ID: 475575 Summary: Underscores display as spaces in the window title bar Classification: I don't know Product: kde Version: unspecified Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: unassigned-b...@kde.org Reporter: r...@rekurs.io Target Milestone: --- SUMMARY Underscores display as spaces in the window title bar. Haven't noticed this happening elsewhere like when alt tabbing for example. Easily reproduced with any program that puts the current file/directory in the title. SOFTWARE/OS VERSIONS Linux: Arch Linux KDE Plasma Version: 5.27.8 KDE Frameworks Version: 5.110.0 Qt Version: 5.15.11 -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 475575] Underscores display as spaces in the window title bar
https://bugs.kde.org/show_bug.cgi?id=475575 Riku changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #2 from Riku --- Seems to be any program for me, including dolphin. Using breeze decorations. Looks like underscores are fine on oxygen or plastik. -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 475575] Underscores display as spaces in the window title bar
https://bugs.kde.org/show_bug.cgi?id=475575 --- Comment #4 from Riku --- Created attachment 162353 --> https://bugs.kde.org/attachment.cgi?id=162353&action=edit Demonstration of the issue -- You are receiving this mail because: You are watching all bug changes.
[kde] [Bug 475575] Underscores display as spaces in the window title bar
https://bugs.kde.org/show_bug.cgi?id=475575 Riku changed: What|Removed |Added Status|NEEDSINFO |REPORTED Resolution|WAITINGFORINFO |--- --- Comment #5 from Riku --- Added a video. I should have mentioned before that this only started happening recently. -- You are receiving this mail because: You are watching all bug changes.
[Breeze] [Bug 475575] Underscores display as spaces in the window title bar
https://bugs.kde.org/show_bug.cgi?id=475575 --- Comment #8 from Riku --- I use DejaVu sans size 8, no scaling. Tried setting the window title size to 10 in system settings -> appearance -> fonts, and the underscores show up now. -- You are receiving this mail because: You are watching all bug changes.
[kwin] [Bug 476570] Bad frametime with Nvidia 545.29.02 on X11
https://bugs.kde.org/show_bug.cgi?id=476570 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[plasmashell] [Bug 402912] Panel in "Auto-Hide" mode does not auto-hide when KWin HideUtilityWindowsForInactive is false
https://bugs.kde.org/show_bug.cgi?id=402912 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 463187] New: Cursor rendering bug
https://bugs.kde.org/show_bug.cgi?id=463187 Bug ID: 463187 Summary: Cursor rendering bug Classification: Applications Product: konsole Version: 22.12.0 Platform: Archlinux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: font Assignee: konsole-de...@kde.org Reporter: r...@rekurs.io Target Milestone: --- Created attachment 154668 --> https://bugs.kde.org/attachment.cgi?id=154668&action=edit Example SUMMARY A couple of pixels appear in the top left corner of the window. Seems to be caused by the cursor rendering somehow as it's affected by the cursor shape and color. STEPS TO REPRODUCE Run konsole with the cursor set to block and make the window inactive. Alternatively, happens always with I-beam. Does not happen with underscore. SOFTWARE/OS VERSIONS KDE Plasma Version: 5.26.4 KDE Frameworks Version: 5.101.0 Qt Version: 5.15.7 ADDITIONAL INFORMATION Tested on a fresh install. Also tried downgrading and looks like it didn't happen before version 22.11.80. -- You are receiving this mail because: You are watching all bug changes.
[konsole] [Bug 462421] Pixel (0, 0) is rendered black when window is inactive
https://bugs.kde.org/show_bug.cgi?id=462421 Riku changed: What|Removed |Added CC|r...@rekurs.io | -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 487629] Double-clicking mouse Forward/Back button opens files/folders
https://bugs.kde.org/show_bug.cgi?id=487629 Riku changed: What|Removed |Added CC||r...@rekurs.io -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 497803] Minimizing dolphin and tabbing back in focuses the places panel
https://bugs.kde.org/show_bug.cgi?id=497803 --- Comment #2 from Riku --- Created attachment 177027 --> https://bugs.kde.org/attachment.cgi?id=177027&action=edit Demonstration Looks like this only happens on X11. -- You are receiving this mail because: You are watching all bug changes.
[dolphin] [Bug 497803] New: Minimizing dolphin and tabbing back in focuses the places panel
https://bugs.kde.org/show_bug.cgi?id=497803 Bug ID: 497803 Summary: Minimizing dolphin and tabbing back in focuses the places panel Classification: Applications Product: dolphin Version: 24.12.0 Platform: Arch Linux OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: general Assignee: dolphin-bugs-n...@kde.org Reporter: r...@rekurs.io CC: kfm-de...@kde.org Target Milestone: --- SUMMARY Tabbing into dolphin after it had been minimized puts the places panel in focus instead of the files themselves. I tend to navigate with a keyboard by typing the directory/file names so this has been quite aggravating. As a workaround you can just not minimize the window or hide the places panel. STEPS TO REPRODUCE 1. Minimize dolphin 2. Tab back in 3. Type something OBSERVED RESULT After the window is raised the places panel steals focus and eats your input. EXPECTED RESULT Focus should be on the files. SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.2.4 KDE Frameworks Version: 6.9.0 Qt Version: 6.8.1 Graphics Platform: X11 -- You are receiving this mail because: You are watching all bug changes.
[Powerdevil] [Bug 358957] laptop won't hybrid-suspend when Plasma is running
https://bugs.kde.org/show_bug.cgi?id=358957 Riku Voipio changed: What|Removed |Added CC||nc...@kos.to --- Comment #14 from Riku Voipio --- systemctl has actions sleep, hybrid-sleep, hibernate, poweroff. I think making menu for lid actions match this would keep both the code and UI simpler than the checkbox option. But any form of hybrid-sleep support would be preferred. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance
https://bugs.kde.org/show_bug.cgi?id=356357 --- Comment #6 from Riku Voipio --- (In reply to kdeu from comment #5) > https://linux.die.net/man/1/ionice > Baloo's priority is set to Idle, which means it should not cause "abusive" > disk activity. ionice is being used, and it does a good job to makes sure the crawling activity happens at lower priority than other use. The effect of ionice is ruined by aggressive fdatasync usage when writing the large LMDB database. It appears fdatasync causes disk writes from a kernel thread that has collected all buffered disk writes. Buffers don't carry the iopriority info on them. Kernel thread just sees the red flag "please commit this data ASAP" and then thinks "to keep FS consistent, I should also commit lots of other unwritten pages just to be sure". Try the patch I made. The disk light still flashes like mad but it doesn't ruin interactive use anymore. Iopriority works as expected until you ask the kernel to be sure writes get to disk too. (In reply to kdeu from comment #3) > I'm not sure if I should keep this bug open or what. Specially since this is > probably only a problem during first run. It also appears when doing operations like switching branches in huge git trees (linux, chromium), copying directories etc. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance
https://bugs.kde.org/show_bug.cgi?id=356357 --- Comment #8 from Riku Voipio --- (In reply to kdeu from comment #7) > Are there any experiences whith using LMDB and NOSYNC? Personally I've happily used that with patch attached since filing this bug - except for a handful of upgrades when I forgot the patch, only to notice that suddenly the disk light flashing means jittery UI again. Baloo makes finding files from local HD almost as easy as finding public files with google. It's really sad if people disable baloo because it's causing the desktop freeze and stutter. > Are there tools/ways to recover a corrupted database or lost transactions > with LMDB? They might not even exist yet, if people don't use NOSYNC. You are assuming that under current configuration LMDB can't get corrupted. File systems are nasty and even with fdatasync there are caveats. But for most users, sudden crashes (especially in middle of transactions) is really rare events. Lost transactions are not a problem, entries would be just regenerated in next index scanning. Recovering the DB is somewhat pointless - you can just regenerate it from scratch, if under idle iopriority the indexing really has no user impact. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 356357] New: Continous index flushing with fdatasync degrades interactive performance
https://bugs.kde.org/show_bug.cgi?id=356357 Bug ID: 356357 Summary: Continous index flushing with fdatasync degrades interactive performance Product: Baloo Version: unspecified Platform: Other OS: Linux Status: UNCONFIRMED Severity: normal Priority: NOR Component: Baloo File Daemon Assignee: m...@vhanda.in Reporter: nc...@kos.to CC: pinak.ah...@gmail.com While baloo is indexing, the KDE UI becomes periodically unresponsive. While stracing the baloo_file_extractor, it is apparent the unresponsiveness happens when fdatasync() is called: 59872 pwrite(16, "D\16\6\0\0\0\0\0\t\25\4\0\303\2\0\0\1\10\0\0\26\1\0\1\1\10\0\0E\1\0\1"..., 2895872, 1625571328) = 2895872 pwrite(16, "\377w\6\0\0\0\0\0\240\376\4\0\254\3\0\0\1\10\0\0\26\1\0\1\1\241P\1\10\0\0 "..., 3850240, 1736437760) = 3850240 fdatasync(16, ... It would be better to use MDB_NOSYNC and regenerate the index in the extremely unlikely event of database corruption. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance
https://bugs.kde.org/show_bug.cgi?id=356357 --- Comment #1 from Riku Voipio --- Created attachment 95923 --> https://bugs.kde.org/attachment.cgi?id=95923&action=edit disable sync to make baloo indexing less intrusive This patch made indexing unnoticeable in UI. As side effect, indexing is a lot faster as it doesn't pause to sync all the time. -- You are receiving this mail because: You are watching all bug changes.
[Baloo] [Bug 356357] Continous index flushing with fdatasync degrades interactive performance
https://bugs.kde.org/show_bug.cgi?id=356357 --- Comment #3 from Riku Voipio --- > I'm a little conflicted about this approach since when the index does get > corrupted, it will be impossible for us to detect it. I think it would better to work on detecting and recovering corruption. It's not like a system crash while indexing is the only way the DB can be corrupted. To take a page from the crash-only software ideology[1], the idea is to concentrate in solid recovery rather than preventing crashes and data corruption in first place. [1] https://lwn.net/Articles/191059/ -- You are receiving this mail because: You are watching all bug changes.
