Qt: Could not find any platform plugin

[Ap6661]

If clicking dropdowns or keeping the program open too long, plover crashes with [MainThread] WARNING: Qt: Could not find any platform plugin

{
  inputs,
  ...
}:
{
  flake.homeModules.core =
  { pkgs, lib, ... }:
  let 
    plover-pkg =
    inputs.plover-flake.packages.${pkgs.stdenv.hostPlatform.system}.plover-full.overrideAttrs (old: {
        });
  in
  {
    imports = [ inputs.plover-flake.homeManagerModules.plover ];
    programs.plover = {
      enable = true;
      package = plover-pkg;
    };
  };
}

Using i3

config without the plover.nix file
https://github.com/Ap6661/dotfiles-nix/tree/dendritic

[toyboot4e]

Beautiful config 👀

Would you mind trying this setting? It could resolve the situation (the possibility is low!):

environment.sessionVariables = [
  QT_QPA_PLATFORM = "xcb";
];

By the way, how can I launch Plover with your config? I tried the following, but rofi did not respond in this screen (can't move the cursor):

$ nix build .#nixosConfigurations.nixos.config.system.build.vm
$ ./result/bin/run-nixos-vm
$ # the initial password is ChangeMe
$ # press alt+enter in the VM

[Ap6661]

For some reason rofi does not like being in a vm. Also tons of issues with picom.

You wont be able to see it but if you press
Alt+Shift+Enter to open wezterm and then
pkill picom you should be able to use the terminal to launch and run plover

[Ap6661]

environment.sessionVariables = {
  QT_QPA_PLATFORM = "xcb";
};

sessionVariables is a set so you need {} instead of []

[Ap6661]

The change allows the drop down to open briefly before throwing the error.

Which is progress!!

edit:

After retrying it, that only happened once

[toyboot4e]

Hmm, strange. I would try some random settings.

[Ap6661]

The way I have been forcing it has been Configure > Machine > Machine

[toyboot4e]

Thank you, commenting out the picom config in i3/config.nix allowed rofi to work on VM (i3/home.nix#L44).

However, plover resulted in segmentation fault in my VM. Need more time to check it out..

[toyboot4e]

I failed to setup my VM 😭

@Ap6661 Could you try plover -l debug and see the log?

[Ap6661]

I really need to set up vm builds.

plover.log

[Ap6661]

I set up a vm build that disables some stuff and plover does not encounter that issue anymore.

[toyboot4e]

I've tweaked the setting and it was resolved, too.

For me, it was stylix (and kvantum coming with it) that was causing issue. With QT_DEBUG_PLUGINS=1, it was showing Qt_6_PRIVATE_API not defined error on startup, and Plover was crushing. Strange.

plover-flake should be fixed to work out of the box 🤔

[toyboot4e]

AI says it's due to different version of Qt.

Temporary workaround would be overriding the nixpkgs version:

    plover-flake = {
      url = "github:openstenoproject/plover-flake";
      inputs.nixpkgs.follows = "nixpkgs";
    };

Wow, Plover with neon-like theme!

[Ap6661]

Using the vm build on bare metal fixes the issue too. ?!?!

This is really weird...

OKAY I FIGURED IT ALL OUT!

it only breaks if picom is running.

Did a little more testing and ran picom --config=/dev/null --backend=glx and still crashes. So it looks like if picom is running in any capacity...