[frameworks-kirigami] [Bug 442404] Launching Discover from the Notifier shows both desktop and mobile controls in on the Updates page
https://bugs.kde.org/show_bug.cgi?id=442404 Nate Graham changed: What|Removed |Added CC||ddascalescu+...@gmail.com --- Comment #17 from Nate Graham --- *** Bug 464779 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 442404] Launching Discover from the Notifier shows both desktop and mobile controls in on the Updates page
https://bugs.kde.org/show_bug.cgi?id=442404 Nate Graham changed: What|Removed |Added CC||andy...@mail.ru --- Comment #16 from Nate Graham --- *** Bug 459114 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 442404] Launching Discover from the Notifier shows both desktop and mobile controls in on the Updates page
https://bugs.kde.org/show_bug.cgi?id=442404 Nate Graham changed: What|Removed |Added Resolution|--- |UPSTREAM Status|CONFIRMED |RESOLVED --- Comment #15 from Nate Graham --- (In reply to Aleix Pol from comment #14) > FWIW, there aren't duplicates here or anything, which complaints are you > talking about? Users on social media. I guess they're using distros without the KDE patch collection Sadly I am too; Fedora hasn't shipped it yet. Oh well, since it's fixed in Qt and a fix is available, I guess you're right and we can close this and yell at distros that aren't shipping the fix yet. :) -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 442404] Launching Discover from the Notifier shows both desktop and mobile controls in on the Updates page
https://bugs.kde.org/show_bug.cgi?id=442404 --- Comment #14 from Aleix Pol --- I have not seen this issue since I fixed it in Qt. We can consider reverting the asynchronous Loaders patch if you think distros aren't going to use our Qt patches. It's a bit unfortunate though. Maybe we can somehow detect it at build time? FWIW, there aren't duplicates here or anything, which complaints are you talking about? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 442404] Launching Discover from the Notifier shows both desktop and mobile controls in on the Updates page
https://bugs.kde.org/show_bug.cgi?id=442404 Alex changed: What|Removed |Added CC||alex...@protonmail.com -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 442404] Launching Discover from the Notifier shows both desktop and mobile controls in on the Updates page
https://bugs.kde.org/show_bug.cgi?id=442404 Nate Graham changed: What|Removed |Added Priority|NOR |VHI --- Comment #13 from Nate Graham --- We are getting a lot of user complaints about this. Raising to VHI. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 442404] Launching Discover from the Notifier shows both desktop and mobile controls in on the Updates page
https://bugs.kde.org/show_bug.cgi?id=442404 --- Comment #12 from Arjen Hiemstra --- The more fundamental problem is that the action button loader gets activated while it should simply never be active in desktop mode. This is due to how the globalToolBarStyle property is handled: If it is not explicitly set to toolbar, we always activate the ActionButton. This leads to problems because there is a period of time where the Loader is created and its active property being evaluated while the global toolbar style is still set to the default. In my opinion, the more fundamental fix should be to either have an "unknown" style as default toolbar style, or somehow make sure the global toolbar style property is initialzed before anything that depends on it. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 442404] Launching Discover from the Notifier shows both desktop and mobile controls in on the Updates page
https://bugs.kde.org/show_bug.cgi?id=442404 --- Comment #11 from Aleix Pol --- Another alternative would be to have an: onItemChanged: if (!active) item.destroy() This would keep it async and continue to work as the fix gets merged. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 442404] Launching Discover from the Notifier shows both desktop and mobile controls in on the Updates page
https://bugs.kde.org/show_bug.cgi?id=442404 Nate Graham changed: What|Removed |Added CC||ahiems...@heimr.nl --- Comment #10 from Nate Graham --- I think making it synchronous for now would probably make sense until the fix trickles back to us. What do you think, Arjen? -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 442404] Launching Discover from the Notifier shows both desktop and mobile controls in on the Updates page
https://bugs.kde.org/show_bug.cgi?id=442404 --- Comment #9 from Nate Graham --- Wow, great sleuthing, Aleix! -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 442404] Launching Discover from the Notifier shows both desktop and mobile controls in on the Updates page
https://bugs.kde.org/show_bug.cgi?id=442404 Aleix Pol changed: What|Removed |Added Ever confirmed|0 |1 Status|REPORTED|CONFIRMED --- Comment #8 from Aleix Pol --- Managed to reproduce it and fix it upstream Qt. https://codereview.qt-project.org/c/qt/qtdeclarative/+/372022 Workarounds would be to either mark it a synchronous or add a `visible: active`. Both aren't ideal but better than the status quo. -- You are receiving this mail because: You are watching all bug changes.
[frameworks-kirigami] [Bug 442404] Launching Discover from the Notifier shows both desktop and mobile controls in on the Updates page
https://bugs.kde.org/show_bug.cgi?id=442404 Nate Graham changed: What|Removed |Added Target Milestone|--- |Not decided Version|git-master |Master Assignee|lei...@leinir.dk|notm...@gmail.com Product|Discover|frameworks-kirigami Component|discover|general --- Comment #7 from Nate Graham --- Does not seem to be Discover-specific; moving to Kirigami. -- You are receiving this mail because: You are watching all bug changes.
