Bug 2203323

Fedora Linux 38 entered end-of-life (EOL) status on 2024-05-21.

Fedora Linux 38 is no longer maintained, which means that it
will not receive any further security or bug fix updates. As a result we
are closing this bug.

If you can reproduce this bug against a currently maintained version of Fedora Linux
please feel free to reopen this bug against that version. Note that the version
field may be hidden. Click the "Show advanced fields" button if you do not see
the version field.

If you are unable to reopen this bug, please file a new report against an
active release.

Thank you for reporting this bug and we are sorry it could not be fixed.

The problem remains the same in Fedora 40 with viking-1.10-3.fc40.x86_64.

This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

This package has changed maintainer in Fedora. Reassigning to the new maintainer of this component.

Hello, new maintainer here. I cannot reproduce this issue. I tried given steps in two different ways:

Fedora 40 container:

```
$ distrobox create --image fedora:40 --name fedora-40
$ distrobox enter fedora-40
$ sudo dnf install --assumeyes viking
$ rpm --query viking
viking-1.10-3.fc40.x86_64
$ viking #then reproduce
```

and natively in Fedora 41 Beta with viking-1.10-8.fc41 from https://bodhi.fedoraproject.org/updates/FEDORA-2024-7f46a3ef20

In both cases, the created PDF shows the map.

Could you try once again, just to see if a dependency update fixed this in the meantime? If the issue still happens for you, we have to start hunting for differences.

So it works for you. Interesting! I'm still unable to get anything but blank pages on a fully updated Fedora 40 system.

I'll try to find out what it might be that triggers this.

I tried to install a fresh Fedora Workstation 40 in a virtual machine, install viking, then reproduce. No success, the created PDF showed the map.

It took me some experimenting, but now I believe I have a clue: it is desktop dependent!

If I create a clean account and start a gnome session, it works. If I create a clean account and instead start a Plasma/KDE session, it doesn't work. (These tests were done on the same host, a physical machine used as a workstation. I haven't yet tried in more pristine environments using virtual machines.)

This is not what I expected! I didn't think viking would care about the desktop environment.

As you might guess, Plasma/KDE is my day-to-day environment where I had done all the previous testing. I had tested using containers, but I guess the host environment "shines through" somehow when I open it up enough to start graphical applications. HOW the environment affects this, I don't know. I'll investigate further later on.

Thank you. Using Plasma, I can reproduce too.

I also compiled from upstream master branch (using a Fedora host), exactly the same issue there. So it seems this is not a packaging issue, but either upstream issue, Fedora (as a whole) issue, Plasma issue, or any combination of those.

Curiously, when using the Viking flatpak from Flathub, printing is broken in both GNOME and Plasma, but in the same way that is different from this issue: In both cases, something that looks like a couple of pixels with blurred edges are drawn. So I looks like the flatpak version does not suffer from this particular issue.

It would be interesting to test, in a virtual machine, other distributions as well. I will try that next.

I also tried to find an upstream issue, but could not find one. I have a feeling it is soon the time to file there, too.

This message is a reminder that Fedora Linux 40 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
'version' of '40'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, change the 'version' 
to a later Fedora Linux version. Note that the version field may be hidden.
Click the "Show advanced fields" button if you do not see it.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 40 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora Linux, you are encouraged to change the 'version' to a later version
prior to this bug being closed.

The problem remains in Fedora 42 with viking-1.10-11.fc42.x86_64.

FEDORA-2026-b2b62d44b7 (viking-1.11-1.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-b2b62d44b7

FEDORA-2026-50800f8392 (viking-1.11-2.fc43) has been submitted as an update to Fedora 43.
https://bodhi.fedoraproject.org/updates/FEDORA-2026-50800f8392

FEDORA-2026-50800f8392 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-50800f8392`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-50800f8392

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

FEDORA-2026-50800f8392 (viking-1.11-2.fc43) has been pushed to the Fedora 43 stable repository.
If problem still persists, please make note of it in this bug report.