https://bugs.kde.org/show_bug.cgi?id=451441

Ben <globalun...@disroot.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |globalun...@disroot.org

--- Comment #2 from Ben <globalun...@disroot.org> ---
(In reply to Nate Graham from comment #1)
> If this truly happened after a kernel update, then it's some sort of kernel
> regression. Perhaps the in-kernel NTFS driver exposes the filesystem to us
> differently. I would encourage you to report a bug at
> https://bugzilla.kernel.org. Thanks!

My title post maybe a bit misleading
When i said the problem occured on a kernel update
i did not mean that i had only/exclusively updated
just the kernel
When i get lots of updates for many different packages,
System files etc etc, i of course occasionally get a newer
kernel as well
I did not mean i had personally confirmed that the issue
was only/exclusively as a result of the kernel
I make the educated guess that devs will be able to see
exactly what other packages were also in the update
when the new kernel version came out

The bug still exists and also under Wayland
Dont know why your saying this is "Resolved"

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to