Bug 448023

Summary:	Text becomes blurred when editing
Product:	[Applications] kid3	Reporter:	mat.rode
Component:	general	Assignee:	Urs Fleisch <ufleisch>
Status:	RESOLVED NOT A BUG
Severity:	normal
Priority:	NOR
Version First Reported In:	3.9.x
Target Milestone:	---
Platform:	Mint (Ubuntu based)
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	blurredtexttagedit attachment-1354-0.html

Description mat.rode 2022-01-06 14:28:01 UTC

STEPS TO REPRODUCE
1. open Kid3 with activated qt5/gtk2 theme on Linux Mint 20.2 Kernel 5.11.0-44
2. choose a mp3 file and edit a tag line

OBSERVED RESULT
3. by deleting or overwriting the existing text, the old values are still visible, although a new one has been typed
4. leave the tag with TAB or mouseclick, then it updates graphically the tag with the new value

EXPECTED RESULT
the graphics should show the values like they are typed
with other activated themes this does not occur

SOFTWARE/OS VERSIONS
OS: Linux Mint 20.2 Cinnamon
Theme: Mint-Y-Dark
Kernel: 5.11.0-44

Comment 1 mat.rode 2022-01-06 14:39:57 UTC

Created attachment 145160 [details]
blurredtexttagedit

Comment 2 Urs Fleisch 2022-01-06 17:05:34 UTC

Could you please check if the workaround described in Bug 425959 helps?

Comment 3 mat.rode 2022-01-06 19:59:04 UTC

Created attachment 145171 [details]
attachment-1354-0.html

Hello Urs,

the 425959 decribes exactly the behavior i have too. Selecting fusion-fixes.qss in the stylesheets of the qt5-settings help for me.Thanks a lot for the help, i searched a little bit for equal bug reportings but didnt find the one you send me.The mentioned icon issue i have in KeepassXC, its very curious, but not a problem in kid3 and for you :)Have a nice evening and a great year 2022.
Greetingsmat
 

    Am Donnerstag, 6. Januar 2022, 18:05:37 MEZ hat Urs Fleisch <bugzilla_noreply@kde.org> Folgendes geschrieben:  
 
 https://bugs.kde.org/show_bug.cgi?id=448023

--- Comment #2 from Urs Fleisch <ufleisch@users.sourceforge.net> ---
Could you please check if the workaround described in Bug 425959 helps?