Bug 2442271 - Initial login prompt of putty invisible in Fedora 43
Summary: Initial login prompt of putty invisible in Fedora 43
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: putty
Version: 43
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2026-02-24 11:59 UTC by Frank
Modified: 2026-03-11 00:48 UTC (History)
1 user (show)

Fixed In Version: putty-0.83-4.fc45 putty-0.83-4.fc44 putty-0.83-4.fc43
Clone Of:
Environment:
Last Closed: 2026-03-02 12:45:47 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Frank 2026-02-24 11:59:13 UTC
Description of problem:

When starting a putty session the initial login prompt is invisible.

Version-Release number of selected component (if applicable):
Fedora 43 (both, KDE and "normal" Workstation)
Putty version is 0.83-2.fc43

How reproducible:
Start putty, open a session to any ssh server

Actual results:
initial login prompt not visible

Expected results:
initial login prompt is visible

Additional info:
Reason seems to be that FG and BG colours are the same.


Starting putty in a terminal session causes the following error messages:

putty:50317): GdkPixbuf-WARNING **: 12:18:41.400: Error loading XPM image loader: Image type “xpm” is not supported

putty:50317): GLib-GObject-CRITICAL **: 12:18:41.400: g_object_ref: assertion 'G_IS_OBJECT (object)' failed


Reason for this problem is a missing packet that is not installed:
gdk-pixbuf2-modules-extra

After installation of this additional packet, everything works fine.
This should be defined as packet dependency.

Comment 1 Fedora Update System 2026-03-02 12:41:37 UTC
FEDORA-2026-8e8abbce2a (putty-0.83-4.fc45) has been submitted as an update to Fedora 45.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-8e8abbce2a

Comment 2 Fedora Update System 2026-03-02 12:45:47 UTC
FEDORA-2026-8e8abbce2a (putty-0.83-4.fc45) has been pushed to the Fedora 45 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 3 Fedora Update System 2026-03-02 12:50:56 UTC
FEDORA-2026-9a2381deaa (putty-0.83-4.fc44) has been submitted as an update to Fedora 44.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-9a2381deaa

Comment 4 Fedora Update System 2026-03-02 12:51:39 UTC
FEDORA-2026-b9f8a57d34 (putty-0.83-4.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-b9f8a57d34

Comment 5 Fedora Update System 2026-03-03 00:52:00 UTC
FEDORA-2026-b9f8a57d34 has been pushed to the Fedora 43 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-b9f8a57d34`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-b9f8a57d34

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2026-03-03 02:10:50 UTC
FEDORA-2026-9a2381deaa has been pushed to the Fedora 44 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-9a2381deaa`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-9a2381deaa

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2026-03-11 00:16:04 UTC
FEDORA-2026-9a2381deaa (putty-0.83-4.fc44) has been pushed to the Fedora 44 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2026-03-11 00:48:35 UTC
FEDORA-2026-b9f8a57d34 (putty-0.83-4.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.