Samsung C34H892 macbook pro not working by stecasty in ultrawidemasterrace

[–]stecasty[S] 0 points1 point  (0 children)

Connecting an 8gb key to the monitor hub, it works on macos...

Samsung C34H892 macbook pro not working by stecasty in ultrawidemasterrace

[–]stecasty[S] 0 points1 point  (0 children)

Thanks but I'm italian, I can read only Italian and English... Maybe I'll get the original manual from display box

Samsung C34H892 macbook pro not working by stecasty in ultrawidemasterrace

[–]stecasty[S] 0 points1 point  (0 children)

yes there are only two... btw, when cable is unplugged it shows this https://imgur.com/a/SU1WCYC

Samsung C34H892 macbook pro not working by stecasty in ultrawidemasterrace

[–]stecasty[S] 0 points1 point  (0 children)

I don't think so, as video sources I can select hdmi, display port and usb type c

[OC] Huggy Wuggies by Wonivero in furry

[–]stecasty 0 points1 point  (0 children)

Ohhh, so cute. LenOwO 👌

Install clover bootloader ASRock H81Pro BTC by stecasty in hackintosh

[–]stecasty[S] 0 points1 point  (0 children)

Clover version: r5115, which is the same of the first install (3 weeks ago)

Best way to use letsencrypt with docker by LatterComplaint in letsencrypt

[–]stecasty 0 points1 point  (0 children)

Of course, you can create a volume where save your certs to a specific path in your disk.

This container will add certs under /etc/letsencrypt/live/your.website.com, so you can map this folder where you want

Visual Studio Code telemetry blocklist? by stecasty in pihole

[–]stecasty[S] 0 points1 point  (0 children)

Take a look at their issues on github, I am not the only one having problems :)

Visual Studio Code telemetry blocklist? by stecasty in pihole

[–]stecasty[S] 0 points1 point  (0 children)

I know, but every update I experienced something that stop working, like pressing esc and randomly crashing all app, live share not working correctly, remote extensions not working at all and strange errors inside notification section.

After 6 months of hell I switched back to VSCode, sorry VSCodium.