https://bugs.kde.org/show_bug.cgi?id=492383
Joshua Goins <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|REPORTED |RESOLVED Latest Commit|https://invent.kde.org/netw |https://invent.kde.org/netw |ork/tokodon/-/commit/c0f910 |ork/tokodon/-/commit/469ee2 |a3439e30cb18b375f69ebc61574 |325aabbd294bf4f1358786c0f7d |290caba |b68b471 --- Comment #9 from Joshua Goins <[email protected]> --- Git commit 469ee2325aabbd294bf4f1358786c0f7db68b471 by Joshua Goins. Committed on 31/08/2024 at 21:48. Pushed by redstrate into branch 'release/24.08'. Do not reload accounts when initially setting the application proxy This is quite the sneaky issue, but I think it goes like this: 1. NetworkController is initialized by the QML engine and it's constructor is called 2. setApplicationProxy is called within said constructor 3. AccountManager's reloadAccounts is called, which in turn emits accountsReloaded 4. accountsReloaded can trigger some signal handler in QML, in turn making the QML engine initialize NetworkController again Now setApplicationProxy has an optional parameter used by NetworkController's constructor to prevent this situation from happening in the first place. (cherry picked from commit c0f910a3439e30cb18b375f69ebc61574290caba) M +7 -3 src/network/networkcontroller.cpp M +2 -1 src/network/networkcontroller.h https://invent.kde.org/network/tokodon/-/commit/469ee2325aabbd294bf4f1358786c0f7db68b471 -- You are receiving this mail because: You are watching all bug changes.
