[Touch-packages] [Bug 1374419] Re: [TOPBLOCKER] Threading issue with the MenuModel Updates
** Changed in: indicator-network (Ubuntu Utopic) Status: New => Won't Fix -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1374419 Title: [TOPBLOCKER] Threading issue with the MenuModel Updates Status in indicator-network package in Ubuntu: Fix Released Status in indicator-network source package in Utopic: Won't Fix Status in indicator-network source package in Vivid: Fix Released Status in indicator-network package in Ubuntu RTM: Fix Released Bug description: This and other "corruptions" in the i-network menus is caused by a race condition in the i-network-service GMainLoop synchronization. === Some access points in indicator-network show twice, when they should be merged into a single entry given that security and SSID are the same. See attached screenshot. For example, "Instant Staff" should only show once, not greyed out. There are not multiple APs with different security settings to justify two different entries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1374419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374419] Re: [TOPBLOCKER] Threading issue with the MenuModel Updates
This bug was fixed in the package indicator-network - 0.5.1+14.10.20141031.3~rtm-0ubuntu1 --- indicator-network (0.5.1+14.10.20141031.3~rtm-0ubuntu1) 14.09; urgency=low [ Jussi Pakkanen ] * Use std::quick_exit. (LP: #1381041) [ Marcus Tomlinson ] * Fix GMainLoopDispatch dispatching ordering when. called inside GMainLoop already Fix GMainLoopDispatch locking. Force all signals from external (dbus-cpp) threads through. GMainLoopDispatch (LP: #1374419) [ Antti Kaijanmäki ] * Increase the default timeouts to match industry standards. (LP: #1381041) * Fix GMainLoopDispatch dispatching ordering when. called inside GMainLoop already Fix GMainLoopDispatch locking. Force all signals from external (dbus-cpp) threads through. GMainLoopDispatch (LP: #1374419) -- Ubuntu daily releaseFri, 31 Oct 2014 14:16:08 + ** Changed in: indicator-network (Ubuntu RTM) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1374419 Title: [TOPBLOCKER] Threading issue with the MenuModel Updates Status in “indicator-network” package in Ubuntu: Fix Released Status in “indicator-network” source package in Utopic: New Status in “indicator-network” source package in Vivid: Fix Released Status in “indicator-network” package in Ubuntu RTM: Fix Released Bug description: This and other "corruptions" in the i-network menus is caused by a race condition in the i-network-service GMainLoop synchronization. === Some access points in indicator-network show twice, when they should be merged into a single entry given that security and SSID are the same. See attached screenshot. For example, "Instant Staff" should only show once, not greyed out. There are not multiple APs with different security settings to justify two different entries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1374419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374419] Re: [TOPBLOCKER] Threading issue with the MenuModel Updates
This bug was fixed in the package indicator-network - 0.5.1+15.04.20141103-0ubuntu1 --- indicator-network (0.5.1+15.04.20141103-0ubuntu1) vivid; urgency=low [ CI bot ] * Resync trunk [ Jussi Pakkanen ] * Use std::quick_exit. (LP: #1381041) [ Marcus Tomlinson ] * Fix GMainLoopDispatch dispatching ordering when. called inside GMainLoop already Fix GMainLoopDispatch locking. Force all signals from external (dbus-cpp) threads through. GMainLoopDispatch (LP: #1374419) [ Antti Kaijanmäki ] * Increase the default timeouts to match industry standards. (LP: #1381041) * Fix GMainLoopDispatch dispatching ordering when. called inside GMainLoop already Fix GMainLoopDispatch locking. Force all signals from external (dbus-cpp) threads through. GMainLoopDispatch (LP: #1374419) indicator-network (0.5.1+14.10.20141015-0ubuntu1) 14.09; urgency=low [ Antti Kaijanmäki ] * deadlock if calling unlock() inside ready signal for a modem that does not require unlocking. (LP: #1333121) -- Ubuntu daily releaseMon, 03 Nov 2014 11:48:11 + ** Changed in: indicator-network (Ubuntu Vivid) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1374419 Title: [TOPBLOCKER] Threading issue with the MenuModel Updates Status in “indicator-network” package in Ubuntu: Fix Released Status in “indicator-network” source package in Utopic: New Status in “indicator-network” source package in Vivid: Fix Released Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: This and other "corruptions" in the i-network menus is caused by a race condition in the i-network-service GMainLoop synchronization. === Some access points in indicator-network show twice, when they should be merged into a single entry given that security and SSID are the same. See attached screenshot. For example, "Instant Staff" should only show once, not greyed out. There are not multiple APs with different security settings to justify two different entries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1374419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374419] Re: [TOPBLOCKER] Threading issue with the MenuModel Updates
** Changed in: indicator-network (Ubuntu Utopic) Assignee: (unassigned) => Antti Kaijanmäki (kaijanmaki) ** No longer affects: ubuntu-system-settings (Ubuntu) ** No longer affects: ubuntu-system-settings (Ubuntu Utopic) ** No longer affects: ubuntu-system-settings (Ubuntu Vivid) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1374419 Title: [TOPBLOCKER] Threading issue with the MenuModel Updates Status in “indicator-network” package in Ubuntu: In Progress Status in “indicator-network” source package in Utopic: New Status in “indicator-network” source package in Vivid: In Progress Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: This and other "corruptions" in the i-network menus is caused by a race condition in the i-network-service GMainLoop synchronization. === Some access points in indicator-network show twice, when they should be merged into a single entry given that security and SSID are the same. See attached screenshot. For example, "Instant Staff" should only show once, not greyed out. There are not multiple APs with different security settings to justify two different entries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1374419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374419] Re: [TOPBLOCKER] Threading issue with the MenuModel Updates
** Changed in: ubuntu-system-settings (Ubuntu Utopic) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1374419 Title: [TOPBLOCKER] Threading issue with the MenuModel Updates Status in “indicator-network” package in Ubuntu: In Progress Status in “ubuntu-system-settings” package in Ubuntu: Invalid Status in “indicator-network” source package in Utopic: New Status in “ubuntu-system-settings” source package in Utopic: Invalid Status in “indicator-network” source package in Vivid: In Progress Status in “ubuntu-system-settings” source package in Vivid: Invalid Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: This and other "corruptions" in the i-network menus is caused by a race condition in the i-network-service GMainLoop synchronization. === Some access points in indicator-network show twice, when they should be merged into a single entry given that security and SSID are the same. See attached screenshot. For example, "Instant Staff" should only show once, not greyed out. There are not multiple APs with different security settings to justify two different entries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1374419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374419] Re: [TOPBLOCKER] Threading issue with the MenuModel Updates
** Also affects: indicator-network (Ubuntu Vivid) Importance: Critical Assignee: Antti Kaijanmäki (kaijanmaki) Status: In Progress ** Also affects: ubuntu-system-settings (Ubuntu Vivid) Importance: Undecided Status: Invalid ** Also affects: indicator-network (Ubuntu Utopic) Importance: Undecided Status: New ** Also affects: ubuntu-system-settings (Ubuntu Utopic) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1374419 Title: [TOPBLOCKER] Threading issue with the MenuModel Updates Status in “indicator-network” package in Ubuntu: In Progress Status in “ubuntu-system-settings” package in Ubuntu: Invalid Status in “indicator-network” source package in Utopic: New Status in “ubuntu-system-settings” source package in Utopic: New Status in “indicator-network” source package in Vivid: In Progress Status in “ubuntu-system-settings” source package in Vivid: Invalid Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: This and other "corruptions" in the i-network menus is caused by a race condition in the i-network-service GMainLoop synchronization. === Some access points in indicator-network show twice, when they should be merged into a single entry given that security and SSID are the same. See attached screenshot. For example, "Instant Staff" should only show once, not greyed out. There are not multiple APs with different security settings to justify two different entries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1374419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374419] Re: [TOPBLOCKER] Threading issue with the MenuModel Updates
** Also affects: indicator-network (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: indicator-network (Ubuntu RTM) Status: New => Incomplete ** Changed in: indicator-network (Ubuntu RTM) Status: Incomplete => In Progress ** Changed in: indicator-network (Ubuntu RTM) Importance: Undecided => Critical ** Changed in: indicator-network (Ubuntu RTM) Assignee: (unassigned) => Antti Kaijanmäki (kaijanmaki) -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1374419 Title: [TOPBLOCKER] Threading issue with the MenuModel Updates Status in “indicator-network” package in Ubuntu: In Progress Status in “ubuntu-system-settings” package in Ubuntu: Invalid Status in “indicator-network” package in Ubuntu RTM: In Progress Bug description: This and other "corruptions" in the i-network menus is caused by a race condition in the i-network-service GMainLoop synchronization. === Some access points in indicator-network show twice, when they should be merged into a single entry given that security and SSID are the same. See attached screenshot. For example, "Instant Staff" should only show once, not greyed out. There are not multiple APs with different security settings to justify two different entries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1374419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374419] Re: [TOPBLOCKER] Threading issue with the MenuModel Updates
** Branch linked: lp:~unity-api-team/indicator-network/fix-gmainloop- syncing -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1374419 Title: [TOPBLOCKER] Threading issue with the MenuModel Updates Status in “indicator-network” package in Ubuntu: In Progress Status in “ubuntu-system-settings” package in Ubuntu: Invalid Bug description: This and other "corruptions" in the i-network menus is caused by a race condition in the i-network-service GMainLoop synchronization. === Some access points in indicator-network show twice, when they should be merged into a single entry given that security and SSID are the same. See attached screenshot. For example, "Instant Staff" should only show once, not greyed out. There are not multiple APs with different security settings to justify two different entries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1374419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1374419] Re: [TOPBLOCKER] Threading issue with the MenuModel Updates
** Summary changed: - Threading issue with the MenuModel Updates + [TOPBLOCKER] Threading issue with the MenuModel Updates -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to indicator-network in Ubuntu. https://bugs.launchpad.net/bugs/1374419 Title: [TOPBLOCKER] Threading issue with the MenuModel Updates Status in “indicator-network” package in Ubuntu: In Progress Status in “ubuntu-system-settings” package in Ubuntu: Invalid Bug description: This and other "corruptions" in the i-network menus is caused by a race condition in the i-network-service GMainLoop synchronization. === Some access points in indicator-network show twice, when they should be merged into a single entry given that security and SSID are the same. See attached screenshot. For example, "Instant Staff" should only show once, not greyed out. There are not multiple APs with different security settings to justify two different entries. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-network/+bug/1374419/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp