Spike sweep and real-time analysis modes display black screen above window size

Using Spike 4.0.8 (latest) on Ubuntu 24.04 on Framework 13 with a BB60D (F/W 7) and external Dell 3840×2160 monitor.

If the Spike window exceeds an area of approx 2/3rds of the screen, the analysis area goes black. Therefore, I can have the Spike window wide and short, or tall and narrow, but not full screen or taking up most of the screen.

It feels like there is a fixed buffer size that is being exceeded somewhere.

Appreciate that 24.04 isn’t in the supported OS list, although hopefully as an LTS release you’ll overlook that. I don’t have a 22.04 machine to test against at present.

I also note that when running on the command line, a Qt error is printed to console on exit.

”’
 ./Spike
QMainWindow::saveState(): ‘objectName’ not set for QDockWidget 0x57535d1c86c0 ‘;
QCoreApplication::postEvent: Unexpected null receiver
”’

I attempted to see if there was a help argument for the program to see if there was something I could fix, but segfault.

”’
./Spike –help
Segmentation fault (core dumped)
”’

[Andrew]

btlac,

We compile most of our Linux offerings on Ubuntu 18.04, and while we don’t list 24.04 I have many reports of success from customers. I will update our website to reflect this.

We have tested Spike on 4k monitors before. Do you see the issue when you put Spike on the main laptop display? If yes, does anything change if you disconnect the external monitor? Can you verify you don’t have any outstanding video drivers you can install for your machine? I haven’t seen your issue specifically, (black screen related to window size), but have seen customers report fully white/black windows, and usually updating video drivers resolves the issue.

Regarding the other issue, it should not be an issue, this is a longstanding output that seems benign, and resists our efforts to remove it.

We have a very limited number of command line arguments, help is not one of them. They are listed in the manual, but are generally unrelated to your issue.

• This reply was modified 4 days, 7 hours ago by Andrew.

Hi Andrew,

Thank you for your quick reply and support.

Having explored further, I believe this is related to using Qt5 and the xcb renderer provided under wayland (the default). Logging out and then back in with an xorg session does not result in the chart going black when fullscreen.

In case someone else has the issue:

– The hardware (via fwupdmgr) is up-to-date, as is the software (via apt) and it’s running the latest Ubuntu 6.14 kernel.
– The issue still occurs with additional GPU memory allocated in UEFI / BIOS.
– The issue does not occur on the main display, although that has a smaller resolution.
– The issue does not occur if the 4k display is set to a sufficiently lower resolution, either directly via the resolution, or via fractional scaling at 150% or greater.
– The same behavior is observed on a different 4k screen.
– Attempts to use the Ubuntu-installed version of Qt5’s wayland renderer failed.

Therefore, workarounds if someone is experiencing this:

– Use a scaled or lower resolution
– Use an xorg session rather than wayland

The other issues were reported simply because segfaulting on an unknown command is unusual behaviour.

Also noticed that when running the setup.sh scripts for Spike and VSG60, a series of \n are printed to the console. This is because the -e argument isn’t passed to echo in the script. Doing so makes for prettier output.

Really enjoying the BB60D and Spike – thanks.

Thanks for the follow up and feedback!

I will pass this along to the team.

[Author]

Posts