Bug 488770 - Proprietary license information does not display correctly.
Summary: Proprietary license information does not display correctly.
Status: RESOLVED FIXED
Alias: None
Product: Discover
Classification: Applications
Component: discover (other bugs)
Version First Reported In: unspecified
Platform: Other Linux
: NOR minor
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-20 04:36 UTC by rossdelnay
Modified: 2024-06-21 13:20 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In: 6.1.0
Sentry Crash Report:

Attachments
This is a screenshot of the text being cut off. (335.80 KB, image/png)
2024-06-20 04:36 UTC, rossdelnay 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description rossdelnay 2024-06-20 04:36:05 UTC 
Created attachment 170662 [details]
This is a screenshot of the text being cut off.

SUMMARY
When viewing a proprietary application's description, the text that displays when clicking the Information button next to "License: Proprietary" gets cut off.

STEPS TO REPRODUCE
1. Open Discover
2. Navigate to a proprietary application. For example, Microsoft Edge or Discord
3. Click on the Information button next to the license near the top. (the i inside the circle)

OBSERVED RESULT
The text does not fit inside the pop up box.

EXPECTED RESULT
The text either wraps to a new line or the box should be larger.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 40
KDE Plasma Version: 6.0.5
KDE Frameworks Version: 6.3.0
Qt Version: 6.7.1
Comment 1 Nate Graham 2024-06-20 23:44:08 UTC 
It looks like https://invent.kde.org/plasma/discover/-/commit/d1e361b92063a490a03ffd97624d5cee0bdbeb31 only works with Frameworks 6.4? That would be sad. The situation with Kirigami.Dialog is making me very sad these days. Need to investigate.
Comment 2 Harald Sitter 2024-06-21 11:45:20 UTC 
That fix is only in 6.1 though!
Comment 3 Nate Graham 2024-06-21 13:20:22 UTC 
I thought I was looking at another bug report that was from someone using 6.1, but apparently not. That makes this less sad and more happy: It's fixed in Plasma 6.1, hooray!