SUMMARY When I try to use Open Sans Extrabold or Myriad Pro Condensed fonts for subtitles another variation of the same family is selected. STEPS TO REPRODUCE 1. Open a project with a subtitle in it 2. Open the subtitle config window and choose one of the fonts mentioned above from the drop down. OBSERVED RESULT Another variation of the same family of font is selected. I can use this fonts on 24.12 appimage, so this is a regression.
Hi, We don't ship fonts in the AppImage, and just use the normal system font selector which chooses from what you have installed on your system. So this is almost certainly going to be some change to the font files in your system, or (slightly less likely) to the KDE/Qt font selection logic - but won't be a change to kdenlive as such - we don't care what font you choose, we just pass that on to the settings in the subtitle file - and we don't even render it, that happens externally too. And we definitely do not embed fonts in subtitle files (and almost certainly shouldn't) - so an important thing to note is that whatever font you choose, it *must* be available at rendering time, otherwise (in almost every renderer) some other font that is available will be 'silently' substituted. If you're burning the fonts in at render time in kdenlive, that means you must always have them available on the system you are rendering on - or if you're shipping the subtitle files separately (or embedding them as subtitle files into a stream container like mkv) the font must be available on the device you are playing it on. Can you confirm that you see this difference if you run both AppImages *today* on the same machine, and if you do, can you render a test file to confirm the result from each of them (the rendered appearance of the font, not how the selector behaves) is different. At this stage, my first guess would be that something font related on your system has changed in the meantime, my second is that something got stricter about confirming the actual variation you selected is supported by the font. It's almost certainly not a bug in anything kdenlive has done, but I'm happy to drill down until we know whats really happening here.
I can't directly test this with my current setup at this point. I am running Debian Trixie (which you seem to indicate you are), and I have *lots* of fonts installed for use with titles (mostly the clip kind, I normally ship separate subtitle files so am very conservative about the choice of fonts in those), but I don't have either of the two you're having this issue with.
All this was done today, on the same machine. I run the 24.12 appimage and I can get the font working as it should. Both in the control panel, it shows correctly. And in project monitor and render. If I run it on 25.08 I can select the font (Open Sans Extrabold) from the drop down selector. But once I click on it it shows only "Open sans" and the bold checkbox is marked. So I guess it selects the Open Sans Bold instead of the Extrabold. If I select the Myriad Pro Bold Condensed after I click on it shows only "Myriad Pro" and the bold checbox is marked. And it doesn't show up on the monitor and the render accordingly. I'll attach a video to illustrate.
Created attachment 184984 [details] Video of fonts working correctly on 24.12 appimage.
Created attachment 184985 [details] Video of issue on 25.08 In this video you can see that even though I select the Myriad Pro Condensed Bold font, the font isn't properly selected nor rendered.
Created attachment 184986 [details] Myriad fonts
(In reply to antimidia from comment #6) > Created attachment 184986 [details] > Myriad fonts I attached the myriad fonts I'm using in case anyone wanna try.
The same issue happens with other fonts that have the Condensed or Extra bold variations. I had the same issue with DejaVu and Cantarell fonts. Also tried with Gravity font family and there I can't access the Ultralight and Light variations, it justs fallsback to the regular variation. It seems like the only variations accepted are those there are checkboxes for it: bold, italic, underline and "scratched" (don't know the word in English).
(In reply to antimidia from comment #4) > Created attachment 184984 [details] > Video of fonts working correctly on 24.12 appimage. (Maybe) minor nit - but this shows the font *already* selected (I assume in an older project?), not you still being able to select it. If you do the same test you showed in the 25.08 demo (new project, select it from scratch) with the 24.12 appimage today what happens? And what DE / Distro release (the report says Debian stable - but are you on current Trixie or an older stable release) - your font selection Dialog doesn't look the same as what I have here. > The same issue happens with other fonts that have the Condensed or Extra bold variations. I seem to be able to select Roboto Condensed and similar fonts just fine ...
(In reply to Ron from comment #9) > (In reply to antimidia from comment #4) > > Created attachment 184984 [details] > > Video of fonts working correctly on 24.12 appimage. > > (Maybe) minor nit - but this shows the font *already* selected (I assume in > an older project?), > not you still being able to select it. If you do the same test you showed > in the 25.08 demo > (new project, select it from scratch) with the 24.12 appimage today what > happens? > > And what DE / Distro release (the report says Debian stable - but are you on > current Trixie or an older > stable release) - your font selection Dialog doesn't look the same as what I > have here. > > > The same issue happens with other fonts that have the Condensed or Extra bold variations. > > I seem to be able to select Roboto Condensed and similar fonts just fine ... There are at least a few odd cases, Like Noto Sans Arabic Condensed vs Extra Condensed, which I can 'select' successfully, and look slightly different in the selector dialog, but don't actually seem to render any differently in the monitor - but that is exactly the same for me between 24.12.4 and 25.08.0.
> (Maybe) minor nit - but this shows the font *already* selected (I assume in > an older project?), No, it's the same project. I opened on 24.12 cause it wasn't working on 25.08 and I wanted to check. I was able to successfully select the font and render my project on 24.12. > not you still being able to select it. If you do the same test you showed > in the 25.08 demo I'm able to select it on 24.12, but not on 25.08. > (new project, select it from scratch) with the 24.12 appimage today what > happens? I'm able to select it. > And what DE / Distro release (the report says Debian stable - but are you on > current Trixie or an older I use Gnome on Debian GNU/Linux 13 (trixie). Stable, up to date. > I seem to be able to select Roboto Condensed and similar fonts just fine ... I don't have Roboto installed. But I also have this issue with Lato font family (besides the ones I mentioned before).
What happens if you select the font in 24.12, save the project, then open it in 25.08, do you get the correct font? You can look inside the .ass file to see exactly what has been chosen. If you then try to select it in 25.08 and save it again, does what is in the .ass change? The degree to which we 'do' anything with fonts for this is extremely limited, mostly we just take font details from the font selector and write them to the .ass file. On both the selection side and the rendering side, we are out of the loop and some other code handles that. > It seems like the only variations accepted are those there are checkboxes for it: bold, > italic, underline and "scratched" (don't know the word in English). 'strikethrough' (aka <strike>) - but these shouldn't have any effect on the font *selection*, they just add style tags to the subtitle text as modifiers to the chosen font. Fonts are a complicated mess, some really have Different glyphs for things like condensed and light and bold and italic - and some just expect the renderer to mangle them to apply those alternate styles. My suspicion for the moment is turning toward some sort of conflict between the Gnome chooser and the Qt/KDE font handling about how those things are represented.
(In reply to Ron from comment #12) > What happens if you select the font in 24.12, save the project, then open it > in 25.08, > do you get the correct font? Yes, I do! But if I change it I can't change it back. > You can look inside the .ass file to see exactly what has been chosen. When I do it on 24.12.3 it show the right font. > If you then try to select it in 25.08 and save it again, does what is in the > .ass change? If I do that the ASS file doesn't seem to change. It still shows the condensed style. > My suspicion for the moment is turning toward some sort of conflict between > the Gnome > chooser and the Qt/KDE font handling about how those things are represented. I don't know if this is helpful or relevant but on Kdenlive 24.12.3 when I open the font selector it offers me two fonts: Myriad Pro and Myriad Pro Cond. Under the Myriad Pro there's the "Condensed" style. So there's apparently two different ways of selecting Myriad Pro Condensed.
(In reply to antimidia from comment #13) > (In reply to Ron from comment #12) > > If you then try to select it in 25.08 and save it again, does what is in the .ass change? > > If I do that the ASS file doesn't seem to change. It still shows the condensed style. What do you get in the ASS if you open a new project with 25.08 and try to select that style? Do you get the 'right' style in that new file even if the UI dialog shows it wrong? And if you do, then if you close kdenlive and reopen with that new project, does it then show the right style in the UI? I was a little suspicious watching your screenshots about whether what is shown in the UI is just the text being clipped to not show the whole name. But assumed you were saying it's not rendering correctly too ... > I don't know if this is helpful or relevant but on Kdenlive 24.12.3 when I > open the font selector it offers me two fonts: Myriad Pro and Myriad Pro > Cond. Under the Myriad Pro there's the "Condensed" style. So there's > apparently two different ways of selecting Myriad Pro Condensed. Yeah, that's what I mean about the mess with how various fonts offer those style options. But if the test above shows the right name always ends up in the ASS - but it somehow still renders incorrectly - then we would seem to have two separate things to look at: - how the UI is showing the font name it reads from/sets to that file. - and if it's really rendering incorrectly, what's happening downstream of us (partly in MLT, but mostly in ffmpeg/libass which does the rendering).
> What do you get in the ASS if you open a new project with 25.08 and try to > select that style? > Do you get the 'right' style in that new file even if the UI dialog shows it > wrong? No, I get the wrong style, not the condensed style I selected. > And if you do, then if you close kdenlive and reopen with that new project, > does it then > show the right style in the UI? Nope. I get the wrong style. > > I was a little suspicious watching your screenshots about whether what is > shown > in the UI is just the text being clipped to not show the whole name. But > assumed > you were saying it's not rendering correctly too ... Yeah, it's not rendering correctly. I get the regular style instead of the condensed. I hope this helps.
(In reply to antimidia from comment #15) > > What do you get in the ASS if you open a new project with 25.08 and try to > > select that style? > > Do you get the 'right' style in that new file even if the UI dialog shows it > > wrong? > > No, I get the wrong style, not the condensed style I selected. Ok, so there's an issue with getting your DE font selector to communicate the correct font. We use QFontDialog for that - but from the look of the screencasts you showed, you're getting the GTK platform theme one. > Yeah, it's not rendering correctly. I get the regular style instead of the condensed. I assume it renders just fine in 25.08 when it 'inherits' the correct font setting from 24.12? > I hope this helps. It definitely helps narrow down where we need to look, though it's still not clear to me whether it's some interaction with the GTK+ platform theme, or if something fundamental has changed with QFontDialog. My suspicion is still on the former, if only because you seem to find it fairly easy to find fonts that do this, while I'm not having much luck finding one in the set I have (using Plasma as the DE).
🐛🧹 ⚠️ 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!
🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME.
(In reply to Bug Janitor Service from comment #18) > 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 > days. Closing as RESOLVED WORKSFORME. It's unclear for me what info it was needed. I provided every info requested and I'm willing to provide more. Bug still happens on 25.08.2 flatpak running on Debian 13/Gnome.
(In reply to antimidia from comment #19) > (In reply to Bug Janitor Service from comment #18) > > 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 > > days. Closing as RESOLVED WORKSFORME. > > It's unclear for me what info it was needed. I provided every info requested > and I'm willing to provide more. Bug still happens on 25.08.2 flatpak > running on Debian 13/Gnome. Sorry, that's just what Bugzilla does if the conversation dies down with a bug in NEEDSINFO state, which it kind of still is, this seems like a Qt/platform font selector issue more than a kdenlive bug, and I haven't personally been able to reproduce it (or had time to dig deeper yet) - but I believe what you say you are seeing, so I've reopened this to track what we know about it, until it's clearer exactly who or what to attribute/forward this to.
Git commit 1e180e37433d44314fcb0e30b173be179cc09718 by Jean-Baptiste Mardelle. Committed on 22/10/2025 at 03:55. Pushed by mardelle into branch 'master'. Disable native font dialog in subtitle styles on Linux M +5 -1 src/dialogs/subtitlestyleedit.cpp https://invent.kde.org/multimedia/kdenlive/-/commit/1e180e37433d44314fcb0e30b173be179cc09718
Regarding the use of the native Font selection dialog, I have now disabled it in AppImage and Flatpak so that you should now have the standard Qt Font dialog. I will send you a link for testing once the build is ready.
Please check with the daily dev AppImage available here and let me know if you can select the font correctly now. https://origin.cdn.kde.org/ci-builds/multimedia/kdenlive/master/linux/ Thanks in advance.
Awesome! It works!! Thanks a lot! Em qua, 2025-10-22 às 06:50 +0000, Jean-Baptiste Mardelle escreveu: > https://bugs.kde.org/show_bug.cgi?id=509564 > > Jean-Baptiste Mardelle <jb@kdenlive.org> changed: > > What |Removed |Added > --------------------------------------------------------------------- > ------- > Resolution|--- |WAITINGFORINFO > Status|CONFIRMED |NEEDSINFO > > --- Comment #23 from Jean-Baptiste Mardelle <jb@kdenlive.org> --- > Please check with the daily dev AppImage available here and let me > know if you > can select the font correctly now. > https://origin.cdn.kde.org/ci-builds/multimedia/kdenlive/master/linux/ > Thanks in advance.
Marking as fixed.
Git commit 630cc9866178fb6c1d2d11ce979f63e97b3b2f4a by Jean-Baptiste Mardelle. Committed on 03/11/2025 at 17:46. Pushed by mardelle into branch 'release/25.08'. Disable native font dialog in subtitle styles on Linux M +5 -1 src/dialogs/subtitlestyleedit.cpp https://invent.kde.org/multimedia/kdenlive/-/commit/630cc9866178fb6c1d2d11ce979f63e97b3b2f4a