[GH-ISSUE #2775] [APP BUG]: libpng error: Invalid IHDR data #899

Closed
opened 2026-02-27 21:08:46 +03:00 by kerem · 7 comments
Owner

Originally created by @italoghost on GitHub (Apr 12, 2025).
Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/2775

Checklist

  • I have searched for a similar issue in this repository and did not find one.
  • I am using an official build obtained from releases or updated one of those builds using its in-app updater.

Describe the Bug

Hi! The latest pre-release AppImage has an error when launching:

~/Downloads/shadps4-linux-qt-2025-04-12-b0fe153
❯ ./Shadps4-qt.AppImage
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
libpng error: Invalid IHDR data
fish: Tarefa 1, './Shadps4-qt.AppImage' encerrada pelo sinal SIGSEGV (Address boundary error)

Reproduction Steps

  1. chmod +x Shadps4-qt.AppImage
  2. ./Shadps4-qt.AppImage
  3. See the error.

Expected Behavior

Launch the application.

Specify OS Version

Cachy OS - 6.14.2-2-cachyos

Originally created by @italoghost on GitHub (Apr 12, 2025). Original GitHub issue: https://github.com/shadps4-emu/shadPS4/issues/2775 ### Checklist - [x] I have searched for a similar issue in this repository and did not find one. - [x] I am using an official build obtained from [releases](https://github.com/shadps4-emu/shadPS4/releases) or updated one of those builds using its in-app updater. ### Describe the Bug Hi! The latest pre-release AppImage has an error when launching: ``` ~/Downloads/shadps4-linux-qt-2025-04-12-b0fe153 ❯ ./Shadps4-qt.AppImage libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data libpng error: Invalid IHDR data fish: Tarefa 1, './Shadps4-qt.AppImage' encerrada pelo sinal SIGSEGV (Address boundary error) ``` ### Reproduction Steps 1. `chmod +x Shadps4-qt.AppImage` 2. `./Shadps4-qt.AppImage` 3. See the error. ### Expected Behavior Launch the application. ### Specify OS Version Cachy OS - 6.14.2-2-cachyos
kerem closed this issue 2026-02-27 21:08:47 +03:00
Author
Owner

@tomboylover93 commented on GitHub (Apr 12, 2025):

Do you have libpng installed on your machine (sudo pacman -S libpng)?

<!-- gh-comment-id:2799121228 --> @tomboylover93 commented on GitHub (Apr 12, 2025): Do you have libpng installed on your machine (`sudo pacman -S libpng`)?
Author
Owner

@Enigmatic-Onion commented on GitHub (Apr 12, 2025):

I am encountering the same issue on EndeavourOS (arch-based) and yes libpng is installed.

<!-- gh-comment-id:2799132799 --> @Enigmatic-Onion commented on GitHub (Apr 12, 2025): I am encountering the same issue on EndeavourOS (arch-based) and yes libpng is installed.
Author
Owner

@italoghost commented on GitHub (Apr 13, 2025):

Do you have libpng installed on your machine (sudo pacman -S libpng)?

Yes, I do @tomboylover93, but it shouldn't matter, should it? As I am using the AppImage.

<!-- gh-comment-id:2799222216 --> @italoghost commented on GitHub (Apr 13, 2025): > Do you have libpng installed on your machine (`sudo pacman -S libpng`)? Yes, I do @tomboylover93, but it shouldn't matter, should it? As I am using the AppImage.
Author
Owner

@tomboylover93 commented on GitHub (Apr 13, 2025):

I've tested on my setup (also CachyOS) and I'm having the same issue. I thought this was caused by #2768 but the commit before that PR was merged also has this issue. Does not happen when building from source (clean build, no code changes). I think it's a problem with the environment the AppImages are built and packaged on. Here's a backtrace in case any developers want to look into this:

Thread 1 "shadps4" received signal SIGSEGV, Segmentation fault.
0x00007ffff6a69be5 in ?? () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Gui.so.6
(gdb) bt
#0  0x00007ffff6a69be5 in ?? () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Gui.so.6
#1  0x00007ffff6a73d8e in ?? () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Gui.so.6
#2  0x00007ffff6a74387 in ?? () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Gui.so.6
#3  0x00007ffff676595b in ?? () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Gui.so.6
#4  0x00007ffff676764d in QImageReader::read() () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Gui.so.6
#5  0x00007ffff673a816 in QPixmapIconEngine::addFile(QString const&, QSize const&, QIcon::Mode, QIcon::State) () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Gui.so.6
#6  0x00007ffff67348a9 in QIcon::addFile(QString const&, QSize const&, QIcon::Mode, QIcon::State) () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Gui.so.6
#7  0x00007ffff77ff04e in ?? () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Widgets.so.6
#8  0x00007ffff780a362 in QCommonStyle::standardIcon(QStyle::StandardPixmap, QStyleOption const*, QWidget const*) const () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Widgets.so.6
#9  0x00007ffff788beb5 in QFusionStyle::standardIcon(QStyle::StandardPixmap, QStyleOption const*, QWidget const*) const () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Widgets.so.6
#10 0x00007ffff7947c1d in QMenuBar::QMenuBar(QWidget*) () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Widgets.so.6
#11 0x0000555555b0c746 in ?? ()
#12 0x0000555555b0ac7e in ?? ()
#13 0x0000555555bef1e6 in main ()
<!-- gh-comment-id:2799296789 --> @tomboylover93 commented on GitHub (Apr 13, 2025): I've tested on my setup (also CachyOS) and I'm having the same issue. I thought this was caused by #2768 but the commit before that PR was merged also has this issue. Does not happen when building from source (clean build, no code changes). I think it's a problem with the environment the AppImages are built and packaged on. Here's a backtrace in case any developers want to look into this: ```bash Thread 1 "shadps4" received signal SIGSEGV, Segmentation fault. 0x00007ffff6a69be5 in ?? () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Gui.so.6 (gdb) bt #0 0x00007ffff6a69be5 in ?? () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Gui.so.6 #1 0x00007ffff6a73d8e in ?? () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Gui.so.6 #2 0x00007ffff6a74387 in ?? () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Gui.so.6 #3 0x00007ffff676595b in ?? () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Gui.so.6 #4 0x00007ffff676764d in QImageReader::read() () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Gui.so.6 #5 0x00007ffff673a816 in QPixmapIconEngine::addFile(QString const&, QSize const&, QIcon::Mode, QIcon::State) () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Gui.so.6 #6 0x00007ffff67348a9 in QIcon::addFile(QString const&, QSize const&, QIcon::Mode, QIcon::State) () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Gui.so.6 #7 0x00007ffff77ff04e in ?? () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Widgets.so.6 #8 0x00007ffff780a362 in QCommonStyle::standardIcon(QStyle::StandardPixmap, QStyleOption const*, QWidget const*) const () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Widgets.so.6 #9 0x00007ffff788beb5 in QFusionStyle::standardIcon(QStyle::StandardPixmap, QStyleOption const*, QWidget const*) const () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Widgets.so.6 #10 0x00007ffff7947c1d in QMenuBar::QMenuBar(QWidget*) () from /tmp/.mount_ShadpsALGMKl/usr/bin/../lib/libQt6Widgets.so.6 #11 0x0000555555b0c746 in ?? () #12 0x0000555555b0ac7e in ?? () #13 0x0000555555bef1e6 in main () ```
Author
Owner

@diegolix29 commented on GitHub (Apr 13, 2025):

@jardon i think u could be helpful here no? Sorry for the ping if u cant

<!-- gh-comment-id:2799418296 --> @diegolix29 commented on GitHub (Apr 13, 2025): @jardon i think u could be helpful here no? Sorry for the ping if u cant
Author
Owner

@irunatbullets commented on GitHub (Apr 13, 2025):

I've just hit this issue in Bazzite using emudeck, which installs the appimage.

Edit: I've just downloaded the previous version appimage and it's fine.

<!-- gh-comment-id:2799852845 --> @irunatbullets commented on GitHub (Apr 13, 2025): I've just hit this issue in Bazzite using emudeck, which installs the appimage. Edit: I've just downloaded the previous version appimage and it's fine.
Author
Owner

@italoghost commented on GitHub (Apr 14, 2025):

It has been fixed. I am closing this issue.

<!-- gh-comment-id:2802124869 --> @italoghost commented on GitHub (Apr 14, 2025): It has been fixed. I am closing this issue.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/shadPS4#899
No description provided.