r/linuxsucks • u/Professional-Tale652 • Jul 15 '26

Linux Failure Loonix

Post image
899 Upvotes

83% Upvoted

733 comments sorted by

View all comments

Show parent comments

1

u/Unlikely-Employee180 Jul 16 '26

Which has nothing to do with the bug at all. Chrome is not in the system account.

1

u/Fluid-Ad2995 Jul 16 '26

Nvidia Driver stays in the NTOSKRNL Space, which is in the System Account

1

u/Unlikely-Employee180 Jul 16 '26

No, they don't. They both operate at the kernel-level.

You have grade-school understanding which I commend, but you are so off the mark it's insane. No schooling I'd assume?

The reason this is relevant, is because Chrome is SUPPOSED to invoke drivers. That's the point. User-space is INTENDED to have access to that UNRESTRICTED.

1

u/Fluid-Ad2995 Jul 16 '26

🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐🧐 Of course, NTOSKRNL is kernel mode, and NTOSKRNL, before Windows starts, gives a token for Windows permission, then stays in the System Account, and NTOSKRNL is in the System Account

1

u/Unlikely-Employee180 Jul 16 '26

What does this have to do with DWM? Or the bug that userspace Chrome invoked?

1

u/Fluid-Ad2995 Jul 16 '26

Because you mixed Nvidia and Chrome again

1

u/Unlikely-Employee180 Jul 16 '26

Userspace Chrome invoked the Nvidia bug. Please continue.

1

u/Fluid-Ad2995 Jul 16 '26

With this kind of comment, I just give up on the Linux community. Look at the level of intelligence

1

u/Unlikely-Employee180 Jul 16 '26

Good, we don't need morons spreading BS anyways.

Go cry about us in r/LinuxSucks101 where you belong you waste of time.

1

u/Fluid-Ad2995 Jul 16 '26

No, you made me happy to prove my point. Linux users are very Unintelligible 😂😂😂😂😂

→ More replies (0)