Summary: | Include https://invent.kde.org/qt/qt/qtbase/-/commit/ec68c541a72bde122a1ab5ba89f41b58c370537f in KDE Qt patch collection | ||
---|---|---|---|
Product: | [KDE Neon] neon | Reporter: | Piotr Mierzwinski <piotr.mierzwinski> |
Component: | Packages Unstable Edition | Assignee: | Neon Bugs <neon-bugs> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | jr, nate, neon-bugs, piotr.mierzwinski, sitter |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Neon | ||
OS: | Linux | ||
See Also: | https://bugs.kde.org/show_bug.cgi?id=455540 | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Piotr Mierzwinski
2022-06-24 12:31:08 UTC
*** This bug has been marked as a duplicate of bug 455540 *** (In reply to Nate Graham from comment #1) > > *** This bug has been marked as a duplicate of bug 455540 *** Sorry, I don't understand why you marked this bug as duplication, if I raised it for used by me Linux distribution? As I mentioned below. Antonio Rojas stated that the issue is in upstream, and to be detailed in Qt, which is usually provided by maintainers/packagers of Linux distribution, so I raised bug for "Neon Unstable". I assumed that in KDE organization there are some maintainers/ of Neon who prepare packages for this distribution. Tell me please why this is wrong place, and where should I raise bug? In Ubuntu bug tracker? I marked it as a duplicate of Bug 455540 because it's the same issue as Bug 455540, which is fixed in Qt already. If neon hasn't backported the fix for their patch collection, you need to file a bug report for Neon specifically asking them to do that. *** This bug has been marked as a duplicate of bug 455540 *** Oh! I understand what you meant now. *this* bug is for Neon. Lol. (In reply to Nate Graham from comment #4) > Oh! I understand what you meant now. *this* bug is for Neon. Lol. After recent update seems to work. |