Using /usr/share/wbar/dot.wbar config file

Open the. The lines of text are in groups of three with the first three crucial to operation. The following groups of three are for each individual icon. Above this sets the nearly transparent background image. Notice that around the icons above. This is installed during installation. Above this sets icon size --isize , location, distance between icons --idist , and icon transparency-shading --falpha. Above is the font definition. Easiest thing is to restart the rPI after making the change.

Sorry for the late response, RPi is at the office. I've set the pi to boot to console and no autologon to ensure no sessions were created anywhere. I have now been able to RDP to it with the pi user, logged in normally straight away.

To summarise then; on this platform for currently unknown reasons, the X server can occasionally lock up while initialising the glamor module. Symptoms are Sounds good, can't try the xorg.

Xvnc does the same thing, but black background and it doesn't have the massive delay. The above fixes Xorg RDP, but it does not fix the xvnc error. I only use xorg, but thought you might want to be aware. If so, please let us know, and it would be a good idea to update your post on the Raspberry PI forum. It uses a completely separate VNC server. The most likely reason it's not working for you is that no VNC server is installed.

If the command which Xvnc gives you no output, you haven't got one installed. You can install one with apt install tigervnc-standalone-server. The reasons why we have two backends are largely historic. The Xvnc backend is the original one. The Xorg one is newer and generally more performant, but there are odd cases when Xvnc works better for some users.

That made no difference. I didn't install a separate VNC package though, so that may be why. I understand that it's a separate thing, but you mentioned that it may work instead of using xorg, so I thought I'd just mention that it wont work out of the box.

I only use xorg, so I'm happy with the current option, made a note of it in my documents. For the default user pi the rdp session is unusable, while with a newly created user it works well.

One thing: If I open wide the console, i can write at normal speed, while all the rest is terribly slow: clicking on menus and working with file manager and windows.

By the way: I bootstrap my device in console mode without login, but as far as I know, in the past I used to work with rdp even if the pi user was logged. I can now work with xrdp at full speed but of course the gui is different.

The issue seems related to the default Rasperry Os default Xsession:. I can't help you with that. This version won't because systemd --user can only keep track of one display at once. Your session is slow because the mutter window manager is using special effects to redraw things, and these use a lot of bandwidth. Your solution will work, and there's another one in the thread in this post. I've given feedback to the fcitx developers. Thanks for the explanation shixudong - that makes it a bit clearer what's happening.

We can't fix it here. The package is from the standard repos. See the Ubuntu installation instructions for details. It is available from the repositories:. It is GTK Gnome based but can work in all desktop environments. It does not require a compositing manager to be installed and is therefore quicker and more suitable for low-end hardware systems. It is the default in the Google gOS desktop and is available as a. Download and install from the command-line Terminal :.

Obviously, you could create a menu item with the command line options similar to the examples above , or a batch file that can be automatically started at system startup as a cron event or startup session.

You can also change wbar startup options by editing the configuration file:. See this example configuration file. However, not all options are able to be set from the configuration file and must be run from the command line.