Bug 456083 - Audacity logo is displayed incorrectly
Summary: Audacity logo is displayed incorrectly
Status: RESOLVED DUPLICATE of bug 448234
Alias: None
Product: kde
Classification: I don't know
Component: general (show other bugs)
Version: unspecified
Platform: Flatpak Linux
: NOR minor
Target Milestone: ---
Assignee: Unassigned bugs mailing-list
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-06-28 14:40 UTC by BOF
Modified: 2022-06-29 16:21 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
Aduacity screenshot logo (7.64 KB, image/png)
2022-06-28 14:40 UTC, BOF
Details

Note You need to log in before you can comment on or make changes to this bug.
Description BOF 2022-06-28 14:40:48 UTC
Created attachment 150231 [details]
Aduacity screenshot logo

I have no idea if this is in the right category since I have no idea which part is responsible for that issue.

SUMMARY
The Audacity logo is displayed incorrectly

STEPS TO REPRODUCE
1. Download Audacity
2. View logo in start menu

OBSERVED RESULT
The wave form of the logo is displayed as block (see attached screenshot)

EXPECTED RESULT
The waveform of the logo is displayed as waveform

SOFTWARE/OS VERSIONS
Operating System: KDE neon 5.25
KDE Plasma Version: 5.25.0
KDE Frameworks Version: 5.95.0
Qt Version: 5.15.4
Kernel Version: 5.13.0-51-generic (64-bit)
Graphics Platform: X11
Processors: 16 × AMD Ryzen 7 4800H with Radeon Graphics
Memory: 30.8 GiB of RAM
Graphics Processor: AMD RENOIR
Manufacturer: Micro-Star International Co., Ltd.
Product Name: Bravo 17 A4DDR
System Version: REV:1.0

ADDITIONAL INFORMATION
I reported this bug on the issue tracker of Audacity: https://github.com/audacity/audacity/issues/2964
The issue was closed with the comment "Most likely it's a KDE-related issue, thus we cannot do anything about it."

The version was downloaded as flatpak
Comment 1 Nicolas Fella 2022-06-29 12:40:51 UTC
Probably the logo uses SVG features that Qt's SVG implementation doesn't support
Comment 2 Nate Graham 2022-06-29 16:21:43 UTC

*** This bug has been marked as a duplicate of bug 448234 ***