the issue is that things like the DHT and PeX can leak your own home ip address, and local peer discovery can leak the torrents you're seeding to local network devices.
Mullvad is very privacy oriented, hence it giving this advice.
Willem
joined 2 years ago
on my normal desktop I use the flavor of the day DE, gnome is only used on my 40 inch touchscreen, because its the only one I could imagine being good on a touchscreen
Send them a message? They are usually very helpful, you might be able to either get a model or a replacement part.
A lot of ram is under lifetime warranty, check the manifacturer site (usually a serial lookup is enough).
My mom would probably be very angry if I choose to save her over my wife.
My wife can swim ten times better then me tho, so she probably ends up saving both my mom and me
... And he said it might work on wsl, which is Linux on windows translation layer, including graphics support.
A lot of Linux tooling has opened up to windows users because of it, which would include darling, to run mac apps, via wsl, on windows.
Our cat has a craving for chocolate, milk and everything not good for her.
She's not the brightest bulb
If you run a tidy ship, you could go through the apps you might suspect, there is a "set an alarm" permission under settings -> apps -> app -> permissions -> three dots -> all permissions.
I don't think stopping / clearing app data makes it go away if it's do persistent, so you might have to resort uninstalling the apps that have this permission until it goes away.
Yeah, Beaver City!
If the issue is more prominent when the cursor is showing, it could be the hardware cursor (default on KDE) causing the issue. When you use hardware cursors, the cursor is rendered on a different 'plane' on top of the rest, possibly causing desync. You could try disabling it with a environment variable (I think it was KWIN_FORCE_SW_CURSOR=1), forcing to software render the cursor.
Giving this guy a working computer probably will already ruin his marriage, let alone the internet.
view more: next ›
the last part is one of my biggest annoyances. People just clicking away the dialogs that almost exactly tell what is wrong and at most just say: "yeah of gave me an error but I just clicked it away and it still didn't work".
As a software developer, pretty much every error you see I made there for you to either read or screenshot and send to IT, because I had to pretty much implement each one of them. (usually with a standard library, but it's still a deliberate choice to show it to the user)
Real unexpected errors are hopefully written to logfiles, but that's not always possible (try logging an error when your system disk is no longer available).
addendum: please also include the gibberish at the end of the error, because its likely there for IT or me to find more details of this specific error in the thousands to millions of things that are logged for the software or website.