My x11vnc on Fedora has recently started crashing with the following error:
*** stack smashing detected ***:
This issue seems to come and go for a lot of people with x11vnc. Bugs have been reported, but nobody seems to be able to pin it down. One workaround is to recompile it from source with some memory protections disabled, but that is a lot of work .
I found the following workaround to work: launch x11vnc with
-noxrecord on the end. That’s it!
If you’re supporting an end user on Windows XP, Vista, 7, 8, or 10, and don’t want to completely log them out, you can use Run As on a Command Prompt as an administrator and then run the following:
Now edit your variables and relaunch your application. This is very useful if you find yourself needing to correct the PATH, let’s say, for Java.
I’ve been a Project Fi customer for over 2 years. We went from a Verizon bill of $140+ per month for 2 phones with 800 minutes, 100 texts, and unlimited data to Project Fi with unlimited talk and text and $10/GB on data, with an average bill of $50-55/mo. If you’re always on Wi-Fi, it’s a no-brainer.
Project Fi uses towers from Sprint, TMobile, and US Cellular, switching when the signal from the current carrier gets low. Also, Wi-Fi calling and texting works flawlessly – I’ve even taken calls over satellite Internet.
The only caveat with Project Fi is that you pay for your phone up front, and it has to be a phone that gets its updates directly from Google: the Pixel 2, Pixel 2 XL, Moto X4, Pixel, Pixel XL, Nexus 6P, and Nexus 5X.
Here’s a referral code to get a $20 credit when you join Project Fi! Redeem it at https://g.co/fi/r/JFD22V
Recently on my Chromebook running Crouton, I’ve had trouble running applications using xiwi after entering my chroot. I would receive the following error repeatedly:
write_image: Cannot find shm, moving on…
find_shm: Cannot connect to findnacl daemon. (Connection refused)
I tried re-updating my chroot, checking drivers, reinstalling the crouton integration extension, and none of those worked, but this did:
- Enter the chroot
- Run the following command: chown -R 1000:1000 “$HOME”
Apparently, permissions can get messed up and stop xiwi from functioning properly.