Bug 1909350 - Kfontview fails to read font files
Summary: Kfontview fails to read font files
Keywords:
Status: NEW
Alias: None
Product: Fedora
Classification: Fedora
Component: plasma-workspace
Version: 39
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: KDE SIG
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-19 09:53 UTC by Göran Uddeborg
Modified: 2023-11-28 16:37 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Type: Bug
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Debian BTS 799640 0 None None None 2021-12-24 09:18:41 UTC
KDE Software Compilation 439470 0 NOR CONFIRMED KFontView is unable to open or install a font on Wayland 2021-12-24 09:18:41 UTC

Description Göran Uddeborg 2020-12-19 09:53:57 UTC
Description of problem:
Kfontview, when running under Wayland if it matters, fails to show any font file.

Version-Release number of selected component (if applicable):
plasma-workspace-5.20.4-1.fc33.x86_64

How reproducible:
Every time

Steps to Reproduce:
1.kfontview /usr/share/fonts/dejavu-serif-fonts/DejaVuSerif.ttf

Actual results:
A pop-up-window saying: Could not read font
In the terminal where kfontview was started: kf.kio.core: Url QUrl("file:///usr/share/fonts/dejavu-serif-fonts/DejaVuSerif.ttf") already represents a local file, cancelling job.

Expected results:
A display of the font in the kfontview window.

Additional info:
It seems to happen to all font files. Selecting the file inside kfontview rather than giving it as an argument on the command line gives the same result.

Comment 1 Ben Cotton 2021-11-04 16:46:04 UTC
This message is a reminder that Fedora 33 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 33 on 2021-11-30.
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
Fedora 'version' of '33'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 33 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, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 skierpage 2021-11-09 02:44:09 UTC
This bug is still present in Fedora 35 KDE spin, kfontview version 5.22.5. It makes kfontview useless.

FWIW there's a similar bug report in Debian, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=799640

Comment 3 skierpage 2021-12-08 05:50:59 UTC
The upstream KDE bug is https://bugs.kde.org/show_bug.cgi?id=439470. The bug seems to only occur under Wayland.

The workaround (for me, in Fedora 35 KDE spin) to run kfontview under XWayland is to enter `QT_QPA_PLATFORM=xcb kfontview` in a terminal. Then Help > About Font Viewer > Components displays "The xcb windowing system", and I can open and view .ttf font files.

Comment 4 Ben Cotton 2022-11-29 16:51:06 UTC
This message is a reminder that Fedora Linux 35 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 35 on 2022-12-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 '35'.

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.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora Linux 35 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.

Comment 5 Göran Uddeborg 2022-12-03 22:15:32 UTC
Still present in F37 and plasma-workspace-5.26.4.1-1.fc37.x86_64. (Maybe not surprising, the upstreams bug is also still open.)

Comment 6 Aoife Moloney 2023-11-23 00:04:22 UTC
This message is a reminder that Fedora Linux 37 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora Linux 37 on 2023-12-05.
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 '37'.

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 37 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.

Comment 7 skierpage 2023-11-23 09:40:14 UTC
I think this is fixed in upstream KDE, but perhaps only in Plasma 6. Also, the fixed kfontview still makes X11 calls, so it might only work if the XWayland compatibility code is running.

Comment 8 Göran Uddeborg 2023-11-28 16:37:56 UTC
There seems to be a workaround implemented upstreams relying on XWayland, yes. It is apparently not available in Fedora 39, with plasma-workspace-5.27.9.1-3.fc39.x86_64.


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