inxi | full featured CLI system information tool

For Pulseaudio

1. Ensure the /etc/libao.conf defaults to pulseaudio

   default_driver=pulse

   [or edit or create a local .libao (note the dot as the first character) file in your home directory (this will take precedence over the /etc/libao.conf file which is system wide)]

2. Ensure that the pulseaudio daemon is enabled

   systemctl --user enable pulseaudio.service pulseaudio.socket

The check pulse audio:

Finally I have figured this out. The last problem I had was a DNS problem setting dns server from Azure gateway. To fix this I had to install resolvconf and configure it for dynamic updates.

I had to:

1. install and configure strongswan (best instructions I found)
2. set mss/mtu in the charon configuration (as mentioned in this post)
3. Install & configure resolvconf (as in answer here)
4. Set up network manager vpn (The graphical element for top right of menu)

when that is done I bring up the connection

It turns out this was a known bug: https://bugs.kde.org/show_bug.cgi?id=421632

It should be fixed in the next KDE bugfix release (20.08).

Try

This question can only be partially answered because c doesn't specify colored output, it only knows about text. So solutions are dependent on the target platform and from the comments, it's clear the OP is interested in more than one platform.

I did my own implementation a while back that works in *nix terminals supporting ANSI colors and in a win32 console, which I already referred to in comments, but for an answer, this should be simplified to the bare minimum, so here comes an example:

So I'm glad to get a solution for my issu. First of all I get a new way.

My Dockerfile: FROM python:3.8.0-buster RUN apt-get update RUN apt-get -y install freetds-dev freetds-bin unixodbc-dev tdsodbc

After installing these packages:

Yes, it is about your graphic driver/card. As the error message states, you need your graphic driver to support the GL_EXT_gpu_shader4 extension, which in general comes with openGL 3.2 and higher. Your current driver does not support it and in fact, according to what I found on Intel's support website, your graphic card does not support it. Apart from changing your computer / GPU, I see two options:

1) use software rendering by Mesa: Mesa has a software renderer that would offload all openGL calls to be processed by the Mesa library on CPU. You would get slower rendering, but it would work. I have never used it though, so I can't help you in setting it up, you would have to do some research on how exactly to do it.

2) In case you don't plan to do any complex rendering in VTK, you might be ok with using the old rendering backend which was the default until VTK version 7. It doesn't use anything that requires openGL above 2.1, so it should work fine on your computer. To activate it, change the VTK's CMake variable VTK_RENDERING_BACKEND from openGL2 to openGL and then build VTK anew. It's a bit slower and doesn't have some new cool features, but otherwise it's perfectly functional and will suffice for many applications.

The most common cause of bind stack overflow is a recursive function which calls itself indefinitely (i.e. a bug in the recursion). The second most common cause is a recursive function which is programmed correctly, but calls itself too many times for the Lisp implementation to handle it.

I forget what the stack limit is for SBCL -- it might be 8192 but that's just a guess. You could probably determine it by experiment (if not by reading the SBCL documentation).

In either case you can try to figure out which function or functions are causing trouble via