Pingus requires sdl12-compat to run - black screen on launch

Open Beginner friendly
  • Is something wrong?
#63,374 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
70/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
linux, shell

Research direction

Start by reading the Pingus package files in the Void packages collection and inspect the /usr/bin/pingus launch script mentioned in the report. Check how the package launches pingus.bin and whether it declares the sdl12-compat dependency. Done means Pingus launches with graphics as well as sound after installation, using the reported software-rendering command.

Written by the indexing model from the issue text.

Description

bug needs-testing
Is this a new report?

Yes

System Info

Void 6.18.59_1 x86_64 GenuineIntel notuptodate rrrrrmmF

Package(s) Affected

pingus-0.7.6_14

Does a report exist for this bug with the project's home (upstream) and/or another distro?

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1038535

Expected behaviour

The package should install and run Pingus the game, but it plays the sound without showing the game graphics.

Actual behaviour

Void packages Pingus 0.7.6, and that version is built on the old SDL 1.2, not SDL2 that Void ships now. When launched, Pingus attempts to run with SDL2 so the screen is black but sound plays. So it needs the sdl12-compat package installed.

To run the game currently after installing, the command that would run the same on all monitors would be:

SDL_RENDER_DRIVER=software /usr/bin/pingus.bin --datadir /usr/share/pingus --fullscreen

so that should be placed in the shell script /usr/bin/pingus

I'll try to issue a PR if I can figure it out.

Steps to reproduce
  1. Install, then Launch Pingus
  2. Screen is black (but sound plays)
Dominant language
Shell
Stars
3.5k
Forks
2.8k
Avg merge
1d 19h
Merged PRs (30d)
318

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from void-linux/void-packages

All issues in void-linux/void-packages

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.