Login Page - Create Account

Support Board

Date/Time: Fri, 23 Feb 2024 17:45:27 +0000

[User Discussion] - Linux

View Count: 70951

[2020-10-09 12:22:41]
User921987 - Posts: 230
Thanks again TopDog, AlexPereira and Kiwi for leading us to these solutions.. it's benefiting many people and exactly the kind of help and interaction that keeps this forum and SC/Linux on the leading edge!

Thank you too pal!

It's always a pleasure if you are able to give any help. The Karma of life works extremely well you know :)

Unfortunately it's so common that people open their mouths only when they have something to criticize and if the situation can make them look better. I don't know is it some kind of self esteem problem or what. These people almost never give you any solutions or other helpful information. It's all about argue and who sounds "the better".

So let's keep the help mode on and make us as better traders :)
Date Time Of Last Edit: 2020-10-09 12:50:22
[2020-10-14 21:35:56]
Kiwi - Posts: 372
Living on the bleeding edge.

~ > echo && inxi -v1 && echo && wine --version

Host: home Kernel: 5.4.0-51-generic x86_64 bits: 64
Desktop: KDE Plasma 5.20.0 Distro: KDE neon 20.04 5.20
6-Core: AMD Ryzen 5 3600 type: MT MCP speed: 4200 MHz
min/max: 2200/3600 MHz
Device-1: NVIDIA GP108 [GeForce GT 1030] driver: nvidia v: 450.80.02
Display: x11 server: X.Org 1.20.8 driver: nvidia
resolution: 1920x1080~60Hz, 1920x1080~60Hz
OpenGL: renderer: GeForce GT 1030/PCIe/SSE2 v: 4.6.0 NVIDIA 450.80.02
Local Storage: total: 2.84 TiB used: 1.78 TiB (62.8%)
Processes: 319 Uptime: 48m Memory: 15.65 GiB used: 3.42 GiB (21.9%)
Shell: bash inxi: 3.0.38

wine-5.19 (Staging)

Did get one bug in 5.20 where my autostart scripts don't save but worked around by creating a `.desktop` to call them and added it using autostart - could have written directly to systemd but its interesting to use the distro's version. So, I am feeling the edge there Ganz. Will drop back to older version (image of 5.19) if there are any issues in working hours.
Date Time Of Last Edit: 2020-10-14 21:54:27
[2020-10-17 16:01:34]
ganz - Posts: 1048
fyi: https://subdiff.org/blog/2020/k-win-ft-project-5-20-released/
[2020-10-20 16:17:27]
ertrader - Posts: 630
A brief update: I've completed testing SC/Wine 5.20 and Proton GE with dozens of SC open/close, continuous running 24/7 each and no issues at all for either solution. Also, Proton GE just did an update.

SierraChart Version 2192 64 bit
Wine 5.21 or Proton-5.9-GE-8-ST
Mint Linux 20/Ubuntu 20.04/Cinnamon desktop
Kernel 5.4.0-52 generic
OpenGL X11lib: 1.6.12
AMD Ryzen 7 3800X
GeForce GTX 1660 Nvidia video card driver 455.23.04
Dual Monitors
Internet: 290bps, 23ms ping, Comcast, Houston

Updated to Wine 5.21 and SC 2192. Configuration is stable and working well.
Date Time Of Last Edit: 2020-11-13 01:34:23
[2020-10-25 10:56:06]
ganz - Posts: 1048
[2020-10-28 17:22:13]
ganz - Posts: 1048
[2020-10-29 01:16:00]
Kiwi - Posts: 372
My real issue ganz is that I've got a lot of automation that relies on X functionality that seems to have gone from Wayland in the name of security (the nanny state reaches the desktop).

So I want to be able to search windows, move to window names, get details, send keys and text to the windows, change the windows titles. All these things are very mature in X but suffering from a Jobsian desire to control the user's experience & protect us from ourselves in W.

Does XW solve that or do the W protections still apply?

Actually, the participants in this discussion seem to understand why we should be using X11 until Wayland grows up a bit.


This is kinda cool: I'm not sure if "user hateful" is the right term, but they don't seem to be prioritizing the most basic things people are asking for.

I think this stuff will come to Wayland (it is in Sway but that's a step too far for me) so I will wait for it to mature & flesh out its ecosystem.
Date Time Of Last Edit: 2020-10-29 02:40:33
[2020-10-30 04:07:49]
ganz - Posts: 1048
Hello, sir
All these things are very mature in X but suffering from a Jobsian desire to control the user's experience & protect us from ourselves in W.
"... Wayland is just a protocol, whereas X11 is a protocol and entire system around it. ..."
So you need to choose WM as well.
we should be using X11 until Wayland grows up a bit.
You will be fine till RHEL 7 EOL June 30 2024


but a lot of vendors will be moving to a Wayland based API by this date or so


Date Time Of Last Edit: 2020-10-30 16:09:48
[2020-10-31 00:52:13]
Kiwi - Posts: 372
In life I have discovered two things:

- never underestimate the power of market share
- things often take 3 times as long as I expect

The second is often because of the first even when the incumbent makes huge mistakes. Although change can often surprise (but its never the one you expect (like Trump winning & the US having its 2nd civil war). So, as much as I love Michael's writing and research, unless the compositor / window manager writers do a really nice job of filling out the gaps in wayland I expect to sadly still be using x11 beyond those dates. Don't get me wrong - if I could get a KDE or Mint like environment that supported all the functionality of xbindkeys and xdotools I would be on the bleeding edge of Wayland adopters.

I really must try Sway.

Edit 7/11/2020: I tried Sway with Wayland. I don't see me changing during Joe Biden's term unless someone does some real work to fix Wayland and the required ecosystem. The existence of open bugs on X11 or QT doesn't make them basically unusable and that was my experience of SwayWay. Possibly the gnome/way experience is more robust in the bleeding edge Fedora but gnome limits the user & lacks functionality. I like the promised performance but not the loss of functionality so I'll wait and see.
Date Time Of Last Edit: 2020-11-08 21:59:30
[2020-10-31 04:23:18]
ganz - Posts: 1048

- never underestimate the power of market share
- things often take 3 times as long as I expect
and that was the only reason for me to post here : the market reality

but you are very qualified person so you are free to choose any option on the desk
[2020-11-03 15:02:59]
ganz - Posts: 1048

Currently, there are 1175 open P1 issues in the QTBUG project. 583 of
those issues had that priority set more than one year ago, 342 of those had
their priority set more than two years ago, and 175 of those more than
three years ago.

[2020-11-12 15:28:48]
ertrader - Posts: 630
Some more permanent updates on the X11 issue:


Date Time Of Last Edit: 2020-11-12 15:29:00
[2020-11-13 07:44:34]
User921987 - Posts: 230

I checked the merge and it really is slightly re-worked. Should work better than the original one. We don't know when libx11 1.6.13 is available so for those using the patch in message #312 I'll try to update it soon to version 4.
Date Time Of Last Edit: 2020-11-13 10:58:48
[2020-11-13 18:32:41]
ganz - Posts: 1048
You've pointed at another bunch of bugs.
Thank you, guys.
[2020-11-13 20:51:21]
ertrader - Posts: 630
Thanks TopDog...Relentless at getting rid of bugs and really appreciate it!

On bug jokes:
Microsoft is working on software for self-driving vehicles.
I can't wait until my car suddenly stops in the middle of the highway and reboots to install updates.

So glad we are on Linux and wine...even with a couple bugs that are now fixed...at least for us! :)

Date Time Of Last Edit: 2020-11-13 20:53:51
[2020-11-20 12:11:46]
ganz - Posts: 1048
Compared to Qt 5.15.0, the new Qt 5.15.1 contains more than 400 bug fixes.
Compared to Qt 5.15.1, the new Qt 5.15.2 contains 176 bug fixes.

[2020-11-20 12:23:11]
User921987 - Posts: 230
Thanks to you too. It’s always a pleasure to connect with people who help make things work. The current setup has been working without any problems and it's faster than windows was.
[2020-11-20 22:02:10]
AlexPereira - Posts: 194
@ertrader and @topdog

awesome work on following through on this issue.
actually noticed today that this existed since 2018: https://aur.archlinux.org/packages/libx11-threadsafe/

btw do you guys notice a big slowdown in loading the files for the first time (and only first time SC launches) because of file compression ( message log gets filled with messages like this: File compression not supported on file system. Windows error code 50: Request not supported. ) ?
[2020-11-21 03:13:14]
Sierra Chart Engineering - Posts: 104368
( message log gets filled with messages like this: File compression not supported on file system. Windows error code 50: Request not supported. ) ?
We will take care of this. We apologize for the delay with this.
Sierra Chart Support - Engineering Level

Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy:

For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service:
Sierra Chart Teton Futures Order Routing
Date Time Of Last Edit: 2020-11-21 12:44:41
[2020-11-21 06:10:46]
ganz - Posts: 1048
[ANNOUNCE] libX11 1.7.0
[2020-11-22 00:50:58]
ertrader - Posts: 630
@AlexPereira... I have not noticed any performance issues but there likely is some delay to trap the error and display. Looks like SC will remove it.

@Ganz... thank you. The detail in the update is helpful and encouraging for finally getting it addressed in distributions!
Date Time Of Last Edit: 2020-11-23 12:33:18
[2020-11-23 18:00:48]
AlexPereira - Posts: 194
I think I have to apologize for the previous comment where I said that the "File compression not supported on file system" caused slowdowns. This weekend I did some SC maintenance, installed latest pre-release 2199 and deleted the scid files. After launching SC again and downloading all the data again, everything seems snappy as it was before and no slowdowns.

So all is good now.

BTW .... arch has already the libx11 1.7.0 since the weekend, so ... its already one distro good.
[2020-11-24 07:21:20]
User921987 - Posts: 230
I installed libX11 1.7.0 from the sources (https://www.x.org/releases/individual/lib/libX11-1.7.0.tar.gz) on Linux Debian 10.6 and it works just fine.
Date Time Of Last Edit: 2020-11-24 10:18:47
[2020-11-24 14:07:00]
Ed C. - Posts: 96
I just started running 2195 on Linux (Debian LMDE 3). I am subscribed to Package 5. I have the Denali feed.

I can connect, and the .scid files update once when the charts load, but then stop updating, and I'm not getting market depth data. It looks like some sort of issue with the way the network connection is done.

Anyone else see this, and have any solutions? Thanks!
[2020-11-25 00:10:49]
Kiwi - Posts: 372
Linux networking is about as robust as it gets Ed so it shouldn't be the issue.

I would start by turning off any firewalls you might have running. After that, possibly share the log with Sierra Chart team and seeking support.

To post a message in this thread, you need to log in with your Sierra Chart account:


Login Page - Create Account