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.
Seriously, it's a terrible idea to click any link including the unsubscribe link in spam email. It just confirms that your email is actively in use. Amount of spam will just increase.
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
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.
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.
Factorio flashbacks!
Nope 50. Just counted.
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.
I am wondering why it has to be above ground. Underground or even at ground level would be cheaper, no?
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.
Seriously, it's a terrible idea to click any link including the unsubscribe link in spam email. It just confirms that your email is actively in use. Amount of spam will just increase.
Source: live and learn.
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=waylandGetting 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.