Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

pianobooster: Fix 'Could not find the Qt platform plugin "xcb" in ""' for #105663

Closed
wants to merge 2 commits into from
Closed

pianobooster: Fix 'Could not find the Qt platform plugin "xcb" in ""' for #105663

wants to merge 2 commits into from

Conversation

mannahusum
Copy link

Motivation for this change

Installing and running pianobooster from nixpkgs currently gives the error:
Could not find the Qt platform plugin "xcb" in ""

Things done

Fixed mkDerviation according to #65399

Just executed it afterwards, and it works

  • Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
  • Built on platform(s)
    • NixOS
    • macOS
    • other Linux distributions
  • Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
  • Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
  • Tested execution of all binary files (usually in ./result/bin/)
  • Determined the impact on package closure size (by running nix path-info -S before and after)
  • Ensured that relevant documentation is up to date
  • Fits CONTRIBUTING.md.

@mannahusum mannahusum changed the title Package pianobooster: Fix 'Could not find the Qt platform plugin "xcb" in ""' for pianobooster: Fix 'Could not find the Qt platform plugin "xcb" in ""' for Dec 2, 2020
@ofborg ofborg bot requested a review from cillianderoiste December 2, 2020 07:35
Copy link
Contributor

@drewrisinger drewrisinger left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi @mannahusum! Thanks for your first contribution! This is mostly correct, but there's a few minor problems with it that we need to address:

  • This targets the release-20.09 branch directly. Standard practice is to commit to master branch first and then backport it to release-20.09 (see the Contributing document, basically git checkout -b fix-pianobooster release-20.09 in a new pull request.
  • Assuming that this was on the correct branch, the below change would need to be made to the diff to match standard conventions
  • You might be able to keep this PR and make it meet our conventions by running git rebase --interactive master and deleting everything except the pianobooster commit. Then push & change the target branch at the top of this PR screen. If you don't want to/can't figure out how to do that, close this PR, open a new one with the correct git branching etc, then tag me in it & I'll follow up.

Standard checklist:

  • Diff mostly LGTM
  • Commits: targets release-20.09 branch when it shouldn't, extra pull commit
  • Builds via nix-review, don't see missing xcb (can't fully start b/c I'm running on a headless machine).
https://github.com/NixOS/nixpkgs/pull/105663
1 package built:
pianobooster

$ nix-shell ~/.cache/nixpkgs-review/pr-105663/shell.nix

[nix-shell:~/.cache/nixpkgs-review/pr-105663]$ pianobooster
qt.qpa.xcb: could not connect to display 172.27.64.1:0.0
qt.qpa.plugin: Could not load the Qt platform plugin "xcb" in "" even though it was found.
This application failed to start because no Qt platform plugin could be initialized. Reinstalling the application may fix this problem.

Comment on lines +2 to +3
, alsaLib, ftgl, libGLU, libjack2, qtbase, rtmidi,
mkDerivation
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
, alsaLib, ftgl, libGLU, libjack2, qtbase, rtmidi,
mkDerivation
, alsaLib, ftgl, libGLU, libjack2, qtbase, rtmidi
, mkDerivation

This fits convention better

@mannahusum mannahusum closed this Dec 5, 2020
@mannahusum
Copy link
Author

I will reopen it as a pull request to master including the changes mentioned

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants