Some solid recommendations in there but Evil Dead in there, and before Mouth of Madness? Blasphemy!

My “other app” has the comment section. Can’t say about the official one. Haven’t touched it in years.

Okay thanks! I guees no use in taking the risk. I’ve started the return process.

Okay that also didn’t work.

Huh, excellent idea. I got nothing to lose so…

Sorry, not sure what you’re saying about the replacement. Should I look into replacing the entire pen or just the nib?

I’ve cleaned it twice using dishwasher soap and water, the usual treatment. With full disassembly. But if there’s a more thorough method I’ll be glad to try.

Sorry what issues? I’m using syncthing to sync between a macos laptop, a macos vm, and my main linux desktop. I sync my projects folder with a lot of git repos. Maybe I’ve been lucky so far but no issues with syncthing and git so far

It’s really like magic sometimes

And ping all that data to CCP instead of our corporate overlords? No thanks

I reckon it could be related to the permissions required to write to the usb. Perhaps udev rules could help here?

So last when I was following the issue on github, it would need to be supported by electron first. It’s in the works but for now, and take it with a grain of salt, I think the recommendation in the issue was to add the options in the desktop file or executable of the app yourself.

If you are distributing the app with the flags then just a remainder to set the compatibility of the flags such that it also works with X.

Thanks! I’ve been comparing verious depth estimation models and sonehow missed this

Ah the problem you are describing in wayland actually usually happens only with electron apps. Most of the electron apps require forcing them to run on wayland. They are usually running on X (x-wayland) which cause all sorts of glitches. You can use xeyes to check if the app is using xwayland or not. If eyes move when you move the cursor inside the app then it’s on xwayland.

To resolve the issues for the electron apps I pass these parameters: --enable-features=UseOzonePlatform --ozone-platform=wayland

Getting these args to flatpacks could be a bit tricky. You can usually find Appimages that can allow you to run these apps easily on wayland.

I am also on ver 550.120 so doubt that driver is the issue here.

Finally, thanks for the clear cut answer. I don’t have any experience with training on AMD but the errors from nvidia are usually very obscure.

As for using gpus other than nvidia, there’s a slew of problems. Mostly that on cloud where most of the projects are deployed, our options seem either limited to nvidia gpus, or cloud tpus.

Each AI experiment can cost usually in thousands of dollars and use a cluster of GPUs. We have built and modified our system for fully utilizing such an environment. I can’t even imagine shifting to Amd gpus at this point. The amount of work involved and the red tape shudder

Oh sorry, guess I missed the random drives part. You’re absolutely right in that regard. Also, I use fstab to setup automount, so can’t help op with this.

WTF? I’m automounting my home directory from an external ssd usb for ages now. What is the disaster that could happen you’re referring to?

Do you mean in terms of gaming? I admit that I don’t do much gaming on linux. Usually just development and browsing.

I also use proprietary nvidia drivers if that makes a difference.

Sorry but could you please elaborate. I’ve been using nvidia forever in linux machines both at work and at home. I work in AI so using nvidia gpus is a must. Maybe there’s something that I missed but my experience has been pretty solid so far.

At home I am using openSUSE tumbleweed KDE wayland and at work ubuntu headless.

I don’t see why it won’t play nice with linux but as to if you should buy this laptop… it doesn’t look in a good shape. I am a bit biased as I had poor experience with laptops with gpus. Old laptops can have bent heatsinks so you can’t control the temps no matter what. If yiu are hell bent on buying it then I’d recommend to stress test both gpu and cpu and look for heavy thermal throttling

There should be a git cli client that plays gifs instead of errors.