Bug 508518

That makes no sense that you get a ghostscript warning, ghostscript is not used for anything (unless you are print previewing).

Could you record a video of the whole thing and attach it here?

Created attachment 184381 [details]
recording showing the problem

there is a bit of offscreen where I enter my pin code, but otherwise it shows the problem.
I only see the following on the terminal now:
kf.kio.core.connection: Socket not connected QLocalSocket::PeerClosedError
kf.kio.core: Connection::send() called with connection not inited
kf.kio.core: Connection::send() called with connection not inited
kf.kio.core: Connection::send() called with connection not inited
kf.kio.core: Connection::send() called with connection not inited
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap
QPixmap::scaled: Pixmap is a null pixmap

Created attachment 184382 [details]
signed document

and here is the signed document where the background image of my handwritten signature is no longer visible.

I wanted to see the errors. But i guess you have confirmed there is no Ghostscript message at all.

Which poppler version are you using?

Can you run
file /path/to/the/file/used/as/background.extension
and paste the result here?

(In reply to Albert Astals Cid from comment #4)
> I wanted to see the errors. But i guess you have confirmed there is no
> Ghostscript message at all.
> 
> Which poppler version are you using?
> 
> Can you run
> file /path/to/the/file/used/as/background.extension
> and paste the result here?

$ pacman -Qs poppler
local/poppler 25.08.0-1
    PDF rendering library based on xpdf 3.0
local/poppler-data 0.4.12-2
    Encoding data for the poppler PDF rendering library
local/poppler-glib 25.08.0-1
    Poppler glib bindings
local/poppler-qt5 25.08.0-1
    Poppler Qt5 bindings
local/poppler-qt6 25.08.0-1
    Poppler Qt6 bindings

$ file rcp-signature.png 
rcp-signature.png: PNG image data, 248 x 103, 8-bit/color RGBA, non-interlaced

I've used these images no problem for years... the only blatant issue remaining before was the lack of ETSI
support .... Ad$be isn't pertinent for PAdES/CAdES
but since a short while the background image, very important, has 'disappeared'.

🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!

$ file signature.png
signature.png: PNG image data, 600 x 218, 8-bit/color RGB, non-interlaced

I already gave the poppler versions

Yes, apologies, i need a bit more time to have a look.

[2025-09-07T17:11:35+0200] [ALPM] upgraded poppler (25.08.0-1 -> 25.09.1-1)
[2025-09-07T17:11:35+0200] [ALPM] upgraded poppler-glib (25.08.0-1 -> 25.09.1-1)
[2025-09-07T17:11:38+0200] [ALPM] upgraded poppler-qt5 (25.08.0-1 -> 25.09.1-1)
[2025-09-07T17:11:38+0200] [ALPM] upgraded poppler-qt6 (25.08.0-1 -> 25.09.1-1)

pour info: nouvelle version de poppler, mais pas de différence

please change the priority to HIGH
we absolutely need the visible images as the scanned image contains the seal+signature that must need be visible
with the text about electronic signature.

this is a SERIOUS regression, not just a nice to have.

is there any other trace information or such I can provide?

reverting 61e4f56ea85f6c094eddf7df56cc6eb2d688d7f4 in poppler seems to fix it. Let me see if we can find a fix instead.

https://gitlab.freedesktop.org/poppler/poppler/-/merge_requests/1890 should fix it.