[Bug 1392012] Re: [MIR] libteam
Re-opened, as there's some interest from OEMs in seeing NM teaming support land in 18.04. ** Description changed: Availability: The package is available in universe, built on all architectures. Rationale: - The package is a new (Build-)Depends for network-manager, for network device bonding support. + The package is a new (Build-)Depends for network-manager, for network device teaming (aka user-space bonding) support. Security: Could not find any related security advisories. Quality assurance: The package is well-maintained in Debian and expected to not require extensive effort to maintain in Ubuntu. UI standards: Not applicable. Dependencies: - All build and binary dependencies are in main; with one exception: - - Build-Depends: libjeansson-dev (bug 1392023) + All build and binary dependencies are in main. Standards compliance: The package meets requirements. Maintenance: The package meets requirements. Background information: libteam is a library for communicating with the netlink kernel layer in order to create bonded interfaces. ** Changed in: libteam (Ubuntu) Status: Expired => Confirmed ** Changed in: libteam (Ubuntu) Status: Confirmed => New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to libteam in Ubuntu. https://bugs.launchpad.net/bugs/1392012 Title: [MIR] libteam To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libteam/+bug/1392012/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
** Changed in: qtbase-opensource-src (Ubuntu) Status: Fix Committed => Fix Released ** Changed in: qtbase-opensource-src (Ubuntu) Status: Fix Released => Fix Committed ** Also affects: qtbase-opensource-src (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: qtbase-opensource-src (Ubuntu RTM) Status: New => Fix Released ** Changed in: qtbase-opensource-src (Ubuntu RTM) Assignee: (unassigned) => Tony Espy (awe) ** Changed in: qtbase-opensource-src (Ubuntu RTM) Importance: Undecided => High ** Changed in: qtbase-opensource-src (Ubuntu) Status: Fix Committed => Triaged -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
@Selene Just wanted to confirm that we don't need any more investigation re: your comment #131 ( I think that may be the largest comment # I've seen in a LP bug ), as your latest update to bug #1524133 indicated that you'd isolated the problem to a SIM with an expired data plan? @Timo We should probably close this bug out when OTA8.5 is released, and then push another update to the PPA that contains the updated patch with the desktop crash fix ( bug #1523975 ). I've attached yet another of the version of the patch which just includes the additional wiredDevice NULL check from Lorn's latest patch. @Lorn Thanks again for all the help. Again, once the OTA8.5 update has been released, we can focus on transitioning to the connectivity API based bearer plugin for our next update. ** Patch added: "yet another update to our bearer-mgmt networkmanager patch" https://bugs.launchpad.net/ubuntu-rtm/+source/dbus-cpp/+bug/1480877/+attachment/4533428/+files/net-bearer-nm-disconnect-ap-signals7.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
So the latest changes in Lorn's signals6 patch can be summarized as: 1) remove QNetworkManagerEngine::requestUpdate (), which is a public method which can trigger a WiFi scan request to NM. This method doesn't appear to be called internally by the bearer plugin, so if we think extra WiFi scans are the culprit, there must have been an change to one of our Qt applications which is calling this method. Also as this method wasn't added in the original patch, it's presence can't really be considered a regression. Has anyone attempted to determine if we *are* scanning more often? This could be done manually by running wpa_cli ( as root ), and watching for the frequency of scan events output. It can also be accomplished by looking at the wpa_suppl and/or NM log messages in syslog. And finally, you could also just monitor DBus looking for ScanDone signals from NM. NOTE - I'm pretty sure this patch won't compile unless this method is also removed from qnetworkmanagerengine.h too, but I haven't tried to build it myself... 2) check that wiredDevice pointer is valid before using it to call a method This is the crasher fix when USS/Qt from the PPA gets installed on a desktop. Looks fine to me. 3) remove most of the logic from the engine's parseConnection() method. This method takes a connection path, and creates a private configuration object, and then based upon the underlying device type, may modify the private configuration instance in a device-specific way before returning it to the caller. The device-specific logic in some cases could have side-effects, such as modifying the global accessPointConfigurations hash table and/or the configuredAccessPoint map. Again, this chnage looks reasonable to remove, however I don't see how it could have any impact on power. This code only runs during initialization where all existing system connections are loaded, and whenever a new system connection is added ( ie. a user connects to a new AP or APN ). I'm not sure whether we want to include this the last change if we want to keep the delta as small as possible? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
Just a quick update to mention that the change to the NM bearer plugin seems to have caused a regression when qtbase is installed from the PPA onto a desktop ( for UI development work ). To reproduce, the overlay PPA needs to be added as a software source, then ubuntu-system-settings installed/upgraded ( which pulls in qtbase ). See bug #1523975 for details. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
The latest version of the patch is now in a silo-026, included as part of a new qtbase version 5.4.1+dfsg-2ubuntu11~vivid1. ** Changed in: qtbase-opensource-src (Ubuntu) Status: In Progress => Fix Committed ** Changed in: sync-monitor (Ubuntu RTM) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
The associated version for the dbus-cpp in silo-026 is: 4.3.0+15.04.20151126-0ubuntu1 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
The fix has landed in silo-026, as part of location-services version: 2.1+15.04.20151202.1-0ubuntu1 ** Changed in: location-service (Ubuntu RTM) Status: In Progress => Fix Committed ** No longer affects: sync-monitor (Ubuntu RTM) ** No longer affects: maliit-framework (Ubuntu RTM) ** No longer affects: indicator-network (Ubuntu) ** No longer affects: buteo-syncfw (Ubuntu RTM) ** Also affects: dbus-cpp (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: dbus-cpp (Ubuntu RTM) Status: New => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
@Timo As previously mentioned, I'd like to get this change out as a hot-fix, and then do proper evaluation of the new connectivity API based plugin with the goal to land it as part of OTA9. @Lorn I'll take a look at that the line you mentioned, however we need to draw the line at some point and re-focus on the replacement plugin as mentioned above. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
Note, I've also pushed a new version based on your latest patch to my PPA if anyone's interested in testing before it lands in silo-026: https://launchpad.net/~awe/+archive/ubuntu/ppa -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
@Lorn Thanks for the update. I usually do all my testing on rc-proposed, as it's latest and greatest. I wasn't aware of the "ubuntu-developer" channel. I've tested on rc- proposed/bq-aquaris.en ( #188 ) with the full set of packages from silo-026, and everything seemed good to me. Thar said, I've reviewed your latest changes and they look good to me. Not creating QNetworkManagerInterfaceDevice and DeviceWireless instances definitely gets rid of the a bunch more DBus signal match rules, and unneeded DBus calls. DeviceWireless is still generates PropertiesChanged signals every time a scan finishes... With this code removed, the plugin operates soley on active and system connection updates. Regarding the device adds for 'rmnet' devices on mako, in theory these should've only been happening at start-up time and/or whenever flight- mode is turned off. Anyways, I'm +1 for including your latest revision of the patch. Thanks again for your help! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
@Lorn Can you add some details regarding what image channel you actually used and device for testing? rc-proposed is probably the best base for you to use. The "GetAll" behavior you're describing is similar to what I was seeing with the AccessPoint objects. The code would see a "PropertiesChanged" signal for an access point, and directly issue a blocking "GetAll" call. This should only be done at initial object creation. Once initialized, the properties can be monitored directly via "PropertiesChanged" signals and the included payload. I imagine this is probably what you've done with your patch. I'll review your updates, and confer with some others to see if we defer your additional changes to OTA9, or try to get them in as part of a proposed hot-fix. Thanks again for your help! -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
Here's my updated patch, the only difference is that it includes a DBusConnection disconnect() call in the destructor for QNetworkManagerInterfaceDeviceModem(), which I'd punted on for expediency while testing earlier this week. If doesn't include the IPv6 related fix, as this was fixed in NM already. Our plan is to get this into silo-026 ASAP for testing as a potential hotfix along with the location-services match rules fixes. ** Patch added: "net-bearer-nm-disconnect-ap-signals4.patch" https://bugs.launchpad.net/ubuntu-rtm/+source/location-service/+bug/1480877/+attachment/4524946/+files/net-bearer-nm-disconnect-ap-signals4.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
@Mike Small stutters when transitioning from mobile to WiFi or visa versa, or stutters when scanning. The fixes to location-services and Qt both are applicable to the latter case only... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
@Lorn Did you see this recently? If so, what device and image? As I mentioned, the mobile connection on touch doesn't support IPv6 connections.There was a bug in NM that falsely reported that a default IPv6 route was available, but this was fixed awhile back. Please see bug #1444162 for details. Perhaps this is what you were seeing? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
@Lorn Thanks for the updated patch. The only significant difference besides the DeviceModem destructor fix was the change you mentioned about default routes. Is there a touch- specific bug that this fixes? On our system, the modem connection will never be IPv6, whereas it is possible to get a IPv6 connection for WiFi. Perhaps we keep this separate? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
Here's a new version of the patch with all the access-point related signals removed. It makes no sense for any of this logic to be present in our system, as none of our code attempts to control the network configuration via Bearer Mgmt. With this patch, the plugin will never receive any NM access-point related signals, and therefore it'll never populate it's access point list. Also, as pointed out in other comments, the bearer plugin includes blocking DBus calls that are made in response to every single 'PropertiesChanged' signal sent for an access point, which causes a ripple of DBus traffic every time a scan occurs. @Lorn, if you could look over my patch, I'd appreciate it. It'd be also nice to get some testing from @faenil and @mterry before we push forward with landing plans.I've confirmed that the CPU spikes in the dbus daemon go away completely with the changes. That said, it'd be good to get some independent results. Until we have a silo prep'd for Qt, you can just install the libqt5network5_5.4.1+dfsg-2ubuntu10~awe16_armhf.deb from my PPA: https://launchpad.net/~awe/+archive/ubuntu/ppa/+packages You also probably want to install dbus-cpp and location-services from: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/landing-026 The status of the location-service silo says it needs a rebuild, but the packages in the PPA should be OK for testing. If you have any questions, ask before you install anything. ** Patch added: "New version of QtBase network bearer plugin" https://bugs.launchpad.net/ubuntu-rtm/+source/location-service/+bug/1480877/+attachment/4523258/+files/net-bearer-nm-disconnect-ap-signals2.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
** Changed in: qtbase-opensource-src (Ubuntu) Assignee: (unassigned) => Tony Espy (awe) ** Changed in: qtbase-opensource-src (Ubuntu) Importance: Undecided => High ** Changed in: qtbase-opensource-src (Ubuntu) Status: Confirmed => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
I grabbed your patch and incorporated most of it into my latest patch ( I left out a few of the disconnect calls for some of the other NM interfaces not directly involved in the match rules problem ), however it failed to build... While trying to just pull in the pieces and resolve the conflicts with the additional debug statements I'd added, I managed to remove the wrong function declaration in qnetworkmanagerservice.h. I removed path() from QNetworkManagerInterface instead of QNetworkMangerInterfaceDeviceWireless.I've refreshed the patch and re-pushed to my PPA. Let's hope it builds this time. ** Patch added: "net-bearer-nm-disconnect-ap-signals.patch" https://bugs.launchpad.net/ubuntu-rtm/+source/location-service/+bug/1480877/+attachment/4522331/+files/net-bearer-nm-disconnect-ap-signals.patch -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
And some more details, by adding 'env QDBUS_DEBUG=1' to the unity8 upstart job, I'm getting a lot more detail without having to further modify the code. I'm seeing "Adding rule" log statements produced by QDBusConnectionPrivate, but no corresponding "Removing rule" logs, so sounds like my previous theory is on track ( ie. that reference counting may be the cause ). That said, I'll need to add some more logging and rebuild... Also, while examining the DBus log, it looks like every time the plugin sees a 'PropertiesChanged' message from the AccessPoint, it calls "GetAll", which is pointless as all the changed properties are transmitted with the signal... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
Just a quick update on my debugging. I've verified that the NM bearer plugin's qnetworkmanagerengine class is receiving the 'AccessPointRemoved', is matching them correctly in it's saved list, and is called delete on the QNetworkManagerInterfaceAccessPoint instance. The associated destructor is called, and my new disconnect() method is called, which succeeds. All that aside, the rules are still piling up, so something else is wrong. I took a quick look at the DBusConnection code, and it looks like the signal matches are reference counted, so it's possible that the count is never reaching zero, so the rule isn't actually released... ( see qdbusconnection.cpp and qdbusintegrator.cpp ). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
Note, QNetworkManagerEngine::setupConfigurations() is also suspect as it can get called from a couple of places and has a loops over the current devices and calls deviceAdded(). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
Some more details: - the version of the qtbase package in touch atm is: 5.4.1+dfsg- 2ubuntu10 - I checked and didn't see significant differences in the networkmanager bearer plugin when comparing against 5.5.1, and 5.6. - That said, there's been quite a few changes in the QDBus code, specifically qdbusintegrator.cpp. Some of the changes include modifications to the signal connect/disconnect code. - After some further instrumentation, I *think* I've located the bug. I added more debug logging to the QDBus code, so I see when match rules are added and removed, and when the corresponding connect/disconnect calls are made. What I see is that the bearer plugin is calling DBusConnection::connect() for each AccessPoint object that's added. This results in a single match rule being added, however I see a second call to DBusConnection::connect() for the same object path, which cause the ref count to incremented. When the AccessPoint is removed, disconnect() only gets called once, the ref count is decremented, and the match rule lives on. - I originally thought this was due to the fact that QNetworkManagerEngine::nmRegistered() calls managerInterface->setConnections(), but at a closer the look the former is registering for Qt signals, while the latter registers for the associated DBus signals. - Looking at the constructor of the plugin engine, QNetworkManagerEngine, it connects the serviceRegistered Qt signal to the method nmEnabled(). At the end of the same function, it checks if the service (NM) has already been registered, and if so invokes nmRegistered again via invokeMethod ( that's some Voodoo I don't quite grok ). Looking at the nmRegistered() function, it has a guard which looks like it was copied from ofonoRegisted() as it guards against ofonoManager != NULL, not managerInterface ( which is what gets created in nmRegistered ). I'll add a bit more logging to confirm, but pretty sure this is the cause of the extra match refs, as if nmRegistered() is called twice, it'll cause connect() to be called for AccessPoint objects twice. - I also see twice as many "GetAll" method calls sent for each access point, although I haven't dug into why this is so yet... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to dbus-cpp in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1462664] Re: [Ubuntu Phone] With WIFI = ON the GPS stops
@Thomas What's the client component in this case, and why wasn't it responding? Also, does this still tie into the WiFi state per the original description? -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1462664 Title: [Ubuntu Phone] With WIFI = ON the GPS stops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1462664/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
** Changed in: network-manager (Ubuntu RTM) Status: In Progress => Fix Committed -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1462664] Re: [Ubuntu Phone] With WIFI = ON the GPS stops
@Markcortbass Do you have the latest OTA installed? Which app were you using when you hit the bug? Also, it's possible that bug #1480877 might have something to do with this, as when WiFi is enabled, and HERE Maps is run, a new WiFi scan is triggered every 4-5s, and the resulting spike in DBus traffic can cause hangs in the UI. I'll talk to the location service developers and see if there's a way to read the location service updates from the command-line so that we can get a better test case for this... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1462664 Title: [Ubuntu Phone] With WIFI = ON the GPS stops To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1462664/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
** Branch linked: lp:~phablet-team/network-manager/lp1480877-wifi-rm- dup-scan-signals -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
** Also affects: location-service (Ubuntu) Importance: Undecided Status: New ** Changed in: location-service (Ubuntu) Status: New => Incomplete ** Changed in: network-manager (Ubuntu) Status: Incomplete => In Progress -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
** Also affects: indicator-network (Ubuntu RTM) Importance: Undecided Status: New ** No longer affects: indicator-network (Ubuntu RTM) ** Also affects: network-manager (Ubuntu RTM) Importance: Undecided Status: New ** Changed in: network-manager (Ubuntu RTM) Status: New => In Progress ** Changed in: network-manager (Ubuntu RTM) Assignee: (unassigned) => Tony Espy (awe) ** Changed in: network-manager (Ubuntu) Importance: Undecided => High ** Changed in: network-manager (Ubuntu RTM) Importance: Undecided => High -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices
Note, one other observation noticed this week. If the HERE Maps application is running and WiFi is enabled, it triggers scans every 4-5s. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to location-service in Ubuntu. https://bugs.launchpad.net/bugs/1480877 Title: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1296114] Re: Bluetooth is always enabled after reboot even if it was disabled
So I think this bug should be split into two different bugs. First, the original reporter filed this on an x86 machine running Desktop, not Touch.As urfkill is still not used on the Desktop as of the latest utopic images, I'm splitting this into a urfkill bug for the problems described by myself and Renato on phones, and a rfkill bug for the desktop issue ( although this could actually be a driver/hardware- specific bug vs. a bug in the rfkill package ). Bug #1376063 has been created to track the urfkill problem seen with the phone images and the urfkill task in this bug marked Invalid. All phone-related tags have been copied to the new bug and removed from this bug. ** Tags removed: beta qa-daily-testing rtm14 touch-2014-10-09 ** Changed in: urfkill (Ubuntu) Status: Triaged = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to indicator-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/1296114 Title: Bluetooth is always enabled after reboot even if it was disabled To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-bluetooth/+bug/1296114/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 913736] Re: Thinkpad 410s -- Cannot re-enable Bluetooth after it's been disabled
Based upon my comment #4 which states that 'lsusb' doesn't show a Bluetooth adapter, and the fact that after I recently got my system board replaced and it now does show a Bluetooth adapter, I'm going to mark this bug as invalid. ** Changed in: gnome-bluetooth (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/913736 Title: Thinkpad 410s -- Cannot re-enable Bluetooth after it's been disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/913736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 913736] Re: Thinkpad 410s -- Cannot re-enable Bluetooth after it's been disabled
I'm pretty sure it was from the indicator... but again this was six months back. If I get a chance later today, I can check with a LiveCD. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/913736 Title: Thinkpad 410s -- Cannot re-enable Bluetooth after it's been disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/913736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 913736] Re: Thinkpad 410s -- Cannot re-enable Bluetooth after it's been disabled
Looks like my apport-collect didn't really grab too much more information... Here's the output from 'rfkill list': espy@zappa:% sudo rfkill list [sudo] password for espy: 0: phy0: Wireless LAN Soft blocked: no Hard blocked: no No BT rfkill device is listed... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/913736 Title: Thinkpad 410s -- Cannot re-enable Bluetooth after it's been disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/913736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 913736] Re: Thinkpad 410s -- Cannot re-enable Bluetooth after it's been disabled
So I may have a bit of mud on my face... There may not be an actual BT adapter in this machine, however to save some face, the BT icon was shown on the panel and I did run the settings app to disable/remove it from the panel. I'm pretty I toggled both switches at the time. I've checked 'lsusb', and /proc/acpi/ibm for presence of the bluetooth adapter, but still don't see it. So, this may be an issue that the system falsely advertises BT, allows you to remove it from the panel, and then rightfully doesn't allow you to re-enable. For now, this should be considered low-priority, but I will continue to follow-up on this... -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-bluetooth in Ubuntu. https://bugs.launchpad.net/bugs/913736 Title: Thinkpad 410s -- Cannot re-enable Bluetooth after it's been disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-bluetooth/+bug/913736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 913736] [NEW] Thinkpad 410s -- Cannot re-enable Bluetooth after it's been disabled
Public bug reported: During UDS-P I was experimenting with various settings to reduce power consumption on my Lenonvo Thinkpad 410s. I turned Bluetooth off via the System Settings - Bluetooth panel. I also removed the icon from the panel by turning visibility to Off. This all works great except for the simple fact that I cannot re-enable my Bluetooth anymore. When I re-launch System Settings - Bluetooth, both toggle switches are Off, and the left hand column below includes the text No Bluetooth Adapters found. There seems to be no way to re-enable my Bluetooth now as both switches are disabled and grayed out. I believe this is due to the fact that when BT is disabled, the device disappears from the bus, which leaves nothing for the code to grab in order to re-enable the device. This is a guess on my part, as I haven't yet taken a look at the code... My machine is running 11.10 with all of the latest updates. The version of gnome-control-center on my machine is: gnome-control-center: Installed: 1:3.2.2-0ubuntu1 Candidate: 1:3.2.2-0ubuntu1 ** Affects: gnome-control-center (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/913736 Title: Thinkpad 410s -- Cannot re-enable Bluetooth after it's been disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/913736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 913736] Re: Thinkpad 410s -- Cannot re-enable Bluetooth after it's been disabled
apport information ** Tags added: apport-collected oneiric running-unity ** Description changed: During UDS-P I was experimenting with various settings to reduce power consumption on my Lenonvo Thinkpad 410s. I turned Bluetooth off via the System Settings - Bluetooth panel. I also removed the icon from the panel by turning visibility to Off. This all works great except for the simple fact that I cannot re-enable my Bluetooth anymore. When I re-launch System Settings - Bluetooth, both toggle switches are Off, and the left hand column below includes the text No Bluetooth Adapters found. There seems to be no way to re-enable my Bluetooth now as both switches are disabled and grayed out. I believe this is due to the fact that when BT is disabled, the device disappears from the bus, which leaves nothing for the code to grab in order to re-enable the device. This is a guess on my part, as I haven't yet taken a look at the code... My machine is running 11.10 with all of the latest updates. The version of gnome-control-center on my machine is: gnome-control-center: Installed: 1:3.2.2-0ubuntu1 Candidate: 1:3.2.2-0ubuntu1 + --- + ApportVersion: 1.23-0ubuntu4 + Architecture: i386 + DistroRelease: Ubuntu 11.10 + EcryptfsInUse: Yes + InstallationMedia: Ubuntu 11.04 Natty Narwhal - Release i386 (20110427.1) + Package: gnome-control-center 1:3.2.2-0ubuntu1 + PackageArchitecture: i386 + ProcEnviron: + PATH=(custom, user) + LANG=en_US.UTF-8 + SHELL=/bin/bash + ProcVersionSignature: Ubuntu 3.0.0-14.23-generic-pae 3.0.9 + Tags: oneiric running-unity + Uname: Linux 3.0.0-14-generic-pae i686 + UpgradeStatus: Upgraded to oneiric on 2011-10-29 (71 days ago) + UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare + usr_lib_gnome-control-center: + deja-dup 20.1-0ubuntu0.2 + gnome-bluetooth3.2.0-0ubuntu2 + indicator-datetime 0.3.1-0ubuntu1 ** Attachment added: Dependencies.txt https://bugs.launchpad.net/bugs/913736/+attachment/2664653/+files/Dependencies.txt -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/913736 Title: Thinkpad 410s -- Cannot re-enable Bluetooth after it's been disabled To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/913736/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 654761] Re: Battery life estimation always show estimating... in battery (indicator applet)
Please do not add bug tasks to the Dell project. This project is used to track internal fixes for factory-related hardware enablement. ** Changed in: dell Status: New = Invalid -- Battery life estimation always show estimating... in battery (indicator applet) https://bugs.launchpad.net/bugs/654761 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-power-manager in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 539477] Re: Video out hot key sends super + p + return on many upcoming Dell HP systems
** Changed in: oem-priority Status: New = Confirmed ** Changed in: oem-priority Importance: Undecided = High -- Video out hot key sends super + p + return on many upcoming Dell HP systems https://bugs.launchpad.net/bugs/539477 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 332060] Re: [Feature Request] Add Service Tag and support URL in System Monitor under System
Closing out the Dell project task, as it's used to track non-public HW enablement work. ** Changed in: dell Status: In Progress = Won't Fix -- [Feature Request] Add Service Tag and support URL in System Monitor under System https://bugs.launchpad.net/bugs/332060 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-monitor in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 440253] Re: Pulse audio control panel does not allow for 3, 5.1, 6.1, 7.1 speaker multi channel audio if supported by sound card
I'm assuming this is for Karmic, correct? Can you also name a currently available machine that this bug can easily be reproduced on? Can you describe how the machine supports multiple outputs ( ie. does it actually have 3, 6, 7, or 8 analog outputs, or are these digital output modes )? As of Karmic Beta, the versions of the involved packages are: gnome-media - 2.28.0-0ubuntu1( gnome-volume-control is the app in question ) pulseaudio - 1:0.9.18-0ubuntu3 One of the things we need to realize is that Pulse attempts to build it's user profiles automatically based on the sometime incorrect information passed back from ALSA re: the supported mixer controls. I discussed this briefly with upstream at the Plumber's conference and came away with the idea that for OEMs installs, custom profiles could possibly be created per machine which might improve the user experience, and make multi-channel profiles available. -- Pulse audio control panel does not allow for 3, 5.1, 6.1, 7.1 speaker multi channel audio if supported by sound card https://bugs.launchpad.net/bugs/440253 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 440253] Re: Pulse audio control panel does not allow for 3, 5.1, 6.1, 7.1 speaker multi channel audio if supported by sound card
Once we flesh out more of the details of this bug, we should also solicit an opinion from upstream too. -- Pulse audio control panel does not allow for 3, 5.1, 6.1, 7.1 speaker multi channel audio if supported by sound card https://bugs.launchpad.net/bugs/440253 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 440253] Re: Pulse audio control panel does not allow for 3, 5.1, 6.1, 7.1 speaker multi channel audio if supported by sound card
Again, *if* the low-level ALSA reporting is correct, then usable HW profiles should've been generated. These should include multi-channel output profiles, although I'm not sure if 6.1 and 7.1 are supported. If the correct ALSA controls are not exposed for a particular OEM's machine, then depending upon their level of support, they can work with OEM and/or the HWE teams to fix the problem. -- Pulse audio control panel does not allow for 3, 5.1, 6.1, 7.1 speaker multi channel audio if supported by sound card https://bugs.launchpad.net/bugs/440253 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 408911] Re: Broadcom card unable to connect karmic
Two things... 1. If possible, please try and use an Ethernet connection to update your system to the latest greatest Karmic updates. 2. If you're able to get the system online, then please run the following command from a terminal ( or use Alt-F2 / Run Application ): apport-collect 408911 This will collect debug information from your system which will help us diagnose the problem. -- Broadcom card unable to connect karmic https://bugs.launchpad.net/bugs/408911 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-system-tools in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 384524] Re: gnome-volume-control crashed with SIGSEGV in g_closure_invoke()
Re-tested with gnome-media 2.27.90-0ubuntu1 ( which includes the commit referenced in the upstream Gnome bug which fixes a problem with an un- initialized variable ), I can no longer reproduce the crash. -- gnome-volume-control crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/384524 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 384524] Re: gnome-volume-control crashed with SIGSEGV in g_closure_invoke()
I just hit this running the lastest version of pulse ( 9.0.16-test4 ) and gnome-media ( 2.27.5-0ubuntu1 ), and gnome-bluetooth ( 2.27.8-0ubuntu1 ). I paired my Samsung SBH500 BT headset. I'm running on a new 15 Macbook. I paired the headset, went to Sound Properties Hardware tab, enabled the BT device and configured it for A2DP, then went to the ouput tab and rapidly clicked back and forth between the Internal device ( which also doesn't work on my machine ) and the BT device. Eventually, the applet crashed. I'm going to change the state back to Confirmed. ** Changed in: gnome-media (Ubuntu) Status: Incomplete = Confirmed -- gnome-volume-control crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/384524 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 384524] Re: gnome-volume-control crashed with SIGSEGV in g_closure_invoke()
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/30007623/Dependencies.txt ** Tags added: apport-collected -- gnome-volume-control crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/384524 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 384524] apport-collect data
Architecture: amd64 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: wl nvidia Package: gnome-media 2.27.5-0ubuntu1 PackageArchitecture: amd64 ProcEnviron: SHELL=/bin/bash PATH=(custom, user) LANG=en_US.UTF-8 ProcVersionSignature: Ubuntu 2.6.31-5.24-generic Uname: Linux 2.6.31-5-generic x86_64 UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare -- gnome-volume-control crashed with SIGSEGV in g_closure_invoke() https://bugs.launchpad.net/bugs/384524 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-media in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 404538] Re: gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running()
So I'm still getting the crash with the new code. I tried to pin down the exact crash using g_assert g_warning statements, but wasn't successful. So, one question I have, is how do I easily create a debug version of this code? I tried adding: DEB_BUILD_OPTIONS=debug nostrip nooopt to the debian/rules, but the resultant binary doesn't appear to have any symbols? Is the process of building a debug version of a package documented anywhere on the wiki? -- gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running() https://bugs.launchpad.net/bugs/404538 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 404538] Re: gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running()
It looks like the GvcMixerStream gets unref'd whilst it's still the
default sink.
I attached to gsd using gdb, and caught the crash:
Program received signal SIGSEGV, Segmentation fault.
gvc_mixer_stream_is_running (stream=0x6de170) at gvc-mixer-stream.c:679
679 if (stream-priv-change_volume_op == NULL)
(gdb) bt
#0 gvc_mixer_stream_is_running (stream=0x6de170) at gvc-mixer-stream.c:679
#1 0x7fffea265534 in update_sink (control=0x6de010, info=0x7fffdc40)
at gvc-mixer-control.c:661
#2 0x7fffecd0daa1 in ?? () from /usr/lib/libpulse.so.0
#3 0x7fffecad9bd3 in ?? () from /usr/lib/libpulsecommon-0.9.15.so
#4 0x7fffecada0c9 in pa_pdispatch_run () from
/usr/lib/libpulsecommon-0.9.15.so
#5 0x7fffecd0b8cd in ?? () from /usr/lib/libpulse.so.0
#6 0x7fffecaddcd4 in ?? () from /usr/lib/libpulsecommon-0.9.15.so
#7 0x7fffecf38fda in ?? () from /usr/lib/libpulse-mainloop-glib.so.0
#8 0x749f2a8e in g_main_context_dispatch () from
/usr/lib/libglib-2.0.so.0
#9 0x749f6458 in ?? () from /usr/lib/libglib-2.0.so.0
#10 0x749f68b5 in g_main_loop_run () from /usr/lib/libglib-2.0.so.0
#11 0x778de117 in gtk_main () from /usr/lib/libgtk-x11-2.0.so.0
#12 0x004046a5 in main (argc=1, argv=0x7fffe308) at main.c:489
Here's what the stream looks like:
(gdb) print stream
$1 = (GvcMixerStream *) 0x6de170
(gdb) print *stream
$2 = {parent = {g_type_instance = {g_class = 0x6de380}, ref_count = 0, qdata =
0x}, priv = 0x}
--
gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running()
https://bugs.launchpad.net/bugs/404538
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 404538] Re: gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running()
Sure, I'll give it a try... -- gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running() https://bugs.launchpad.net/bugs/404538 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 404538] Re: gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running()
I grabbed the specified commit and rebuilt using the latest bzr branch ( eg. 2.27.5-0ubuntu1 ). This seems to fix the problem, I can't get the crash to occur anymore. I created a topic branch which contains the new patch, I'll add it to the bug. Please let me know if you'd like to propose it as a merge. ** Branch linked: lp:~awe/gnome-settings-daemon/output-device-crash -- gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running() https://bugs.launchpad.net/bugs/404538 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 404538] Re: gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running()
OK, false positive... the patch in fact doesn't build. I guess I need more than just the single commit. -- gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running() https://bugs.launchpad.net/bugs/404538 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 404538] Re: gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running()
For now, I just modifed the /plugins/media-keys/cut-n-paste/Makefile.in to add the new files. It may not be the right way to do it, but it's gotten me to the point where I'm testing the new code... -- gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running() https://bugs.launchpad.net/bugs/404538 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 405839] [NEW] gnome-settings-daemon crashes when re-connecting Sound Output to BT device
Public bug reported: Binary package hint: gnome-settings-daemon e...@zappa:% lsb_release -rd Description:Ubuntu karmic (development branch) Release:9.10 gnome-settings-daemon 2.27.4-0ubuntu1 While testing both blueman and gnome-bluetooth, I've managed to crash gnome-settings-daemon by changing switching my sound output device from internal to BT to internal, and back finally back to the connected BT device one more time. This last toggle almost always seems to cause gnome-settings-daemon to crash. I'm pretty sure this is what's happening as in the past I've gotten a crash dialog that stated gnome-settings-daemon crashed. Also my toolbar loses it's theming. ProblemType: Bug Architecture: amd64 Date: Tue Jul 28 10:22:33 2009 DistroRelease: Ubuntu 9.10 NonfreeKernelModules: nvidia Package: gnome-settings-daemon 2.27.4-0ubuntu1 ProcEnviron: PATH=(custom, user) LANG=en_US.UTF-8 SHELL=/bin/bash ProcVersionSignature: Ubuntu 2.6.31-4.23-generic SourcePackage: gnome-settings-daemon Uname: Linux 2.6.31-4-generic x86_64 ** Affects: gnome-settings-daemon (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug -- gnome-settings-daemon crashes when re-connecting Sound Output to BT device https://bugs.launchpad.net/bugs/405839 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 405839] Re: gnome-settings-daemon crashes when re-connecting Sound Output to BT device
** Attachment added: Dependencies.txt http://launchpadlibrarian.net/29620368/Dependencies.txt -- gnome-settings-daemon crashes when re-connecting Sound Output to BT device https://bugs.launchpad.net/bugs/405839 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 405839] Re: gnome-settings-daemon crashes when re-connecting Sound Output to BT device
Here's the backtrace. Exact steps to reproduce: 1. install gnome-bluetooth 2. pair connect to an audio headset ( in my case a samsung snh500 ) 3. change sound output to bt via the sound applet : preferences : output tab 4. play some music ( in this case via rhythmbox ) 5. stop playback 6. toggle sound output back to internal ( note, this doesn't work ) 7. toggle sound output back to BT crash Let me know if there's anything else I can add... -- gnome-settings-daemon crashes when re-connecting Sound Output to BT device https://bugs.launchpad.net/bugs/405839 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 405839] Re: gnome-settings-daemon crashes when re-connecting Sound Output to BT device
** Attachment added: gdb settings-daemon backtrace http://launchpadlibrarian.net/29624391/gdb-gsd.txt -- gnome-settings-daemon crashes when re-connecting Sound Output to BT device https://bugs.launchpad.net/bugs/405839 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 405839] Re: gnome-settings-daemon crashes when re-connecting Sound Output to BT device
I'm not sure how I could've done so ( send the bug via apport )? The system didn't seem to detect the crash, so I had to manually run 'ubuntu-bug', and thus it looks like it only attached Dependencies.txt. I don't fully understand how ubuntu-bug works, but do recall that it hooks into apport. Is there something else I can do please let me know... -- gnome-settings-daemon crashes when re-connecting Sound Output to BT device https://bugs.launchpad.net/bugs/405839 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 405839] Re: gnome-settings-daemon crashes when re-connecting Sound Output to BT device
Yes, apport is enabled. Yes, there's a crash for gnome-settings-daemon in /var/crash now. I can re-run to get another one if necessary. -- gnome-settings-daemon crashes when re-connecting Sound Output to BT device https://bugs.launchpad.net/bugs/405839 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 404538] Re: gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running()
I managed to hit this bug by: 1. install gnome-bluetooth 2. pair connect to an audio headset ( in my case a samsung snh500 ) 3. change sound output to bt via the sound applet : preferences : output tab 4. play some music ( in this case via rhythmbox ) 5. stop playback 6. toggle sound output back to internal ( note, this doesn't work ) 7. toggle sound output back to BT crash Let me know if there's anything else I can add... -- gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running() https://bugs.launchpad.net/bugs/404538 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 405839] Re: gnome-settings-daemon crashes when re-connecting Sound Output to BT device
*** This bug is a duplicate of bug 404538 *** https://bugs.launchpad.net/bugs/404538 ** This bug has been marked a duplicate of bug 404538 gnome-settings-daemon crashed with SIGSEGV in gvc_mixer_stream_is_running() -- gnome-settings-daemon crashes when re-connecting Sound Output to BT device https://bugs.launchpad.net/bugs/405839 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-settings-daemon in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 137247] Re: libpam-keyring broken on autologins
I think the check is whether an *encrypted* keyring is being used. If the keyring already has a NULL password, and is in the clear, then nothing needs to be displayed. An alternative to actually changing the key directly would be an explanation of what needs to be changed, additional words about the security implications, and then either instructions on how to change, or a link / button that launches seahorse. Note, the instructions are probably required at minimum, as changing the login keyring password isn't all that intuitive in seahorse. I also had to launch seahorse from the command line because I couldn't find a way to launch it from the UI ( using 9.04 ). So without a button/link that launches it from the dialog, perhaps gdm does have to do all the work. Finally, I'd like to comment that I agree with jp re: disk encryption. Encrypted home dir was made available in Jaunty ( albeit with some minor work on the installer's part ) and will available as an option by default ( at least that's what I've heard ) in Karmic. This seems to me like the better approach for keeping important things on disk safe as opposed to the login keyring approach. -- libpam-keyring broken on autologins https://bugs.launchpad.net/bugs/137247 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 189192] Re: gdmsetup dialog is to big for 1024 x 768 resolution
I just ran into this running UNR Jaunty on a netbook with a 1024x576 screen which seems to be the resolution most of the smaller netbooks are shipping with now. I think if we chose this resolution as our smallest target, we'd be in good shape. -- gdmsetup dialog is to big for 1024 x 768 resolution https://bugs.launchpad.net/bugs/189192 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 261484] Re: Error while copying mounts
** Tags removed: stop-ship -- Error while copying mounts https://bugs.launchpad.net/bugs/261484 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 201797] [NEW] logging disabled if --foreground used
Public bug reported: Binary package hint: gnome-keyring In Hardy, gnome-keyring is launched via dBus as opposed to being exec'd directly by gnome-session as in Gustsy. The dBus conf file for gnome-keyring ( /usr/share/dbus-1/services/org.gnome.keyring.service ) specifies the --foreground option for gnome-keyring. This does two things: - prevents gnome-keyring from forking and becoming a daemon process - prevents prepare_logging() from being called, which effectively disables logging I can't say I fully understand why keyring isn't being run as a daemon, however disabling logging IMHOP is bad. I've been trying to track down keyring related problems in Ubuntu Mobile, and finally ended up having to patch keyring so that prepare_logging() gets called even if foreground is specified ( see attached patch ). Note - I'm using version 2.21.92-0ubuntu1, although I checked the latest code ( gkr-daemon.c ) in SVN and it's identical. ** Affects: gnome-keyring (Ubuntu) Importance: Undecided Status: New -- logging disabled if --foreground used https://bugs.launchpad.net/bugs/201797 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 201797] Re: logging disabled if --foreground used
** Attachment added: Enable logging even if --foreground is spec'd http://launchpadlibrarian.net/12630118/70_enable_logging.patch -- logging disabled if --foreground used https://bugs.launchpad.net/bugs/201797 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-keyring in ubuntu. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 201797] Re: logging disabled if --foreground used
I'm probably going to have to spin a special version for the Mobile PPA ( for this bug, and pre-populating a default password-less keyring ) anyways, so yes, I can wait for the version update. Backporting the fix however might help with future debugging of desktop keyring problems. Your call... -- logging disabled if --foreground used https://bugs.launchpad.net/bugs/201797 You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is a bug assignee. -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
