[Desktop-packages] [Bug 1640320] Re: FTBFS in zesty

[Thomas Voß]

** Branch linked: lp:~thomas-voss/location-service/fix-zesty-ftbfs

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1640320

Title:
  FTBFS in zesty

Status in location-service package in Ubuntu:
  In Progress

Bug description:
  FTBFS in zesty during a no change rebuild against new boost

  Please see build logs at: https://launchpad.net/ubuntu/+source
  /location-service/3.0.0+16.10.20160912-0ubuntu2

  Please help fix this

  [ 10%] Building CXX object 
src/location_service/com/ubuntu/location/CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o
  cd 
/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service/com/ubuntu/location
 && /usr/bin/g++   -DCOM_UBUNTU_LOCATION_SERVICE_HAVE_NET_CPP=1 
-DCOM_UBUNTU_LOCATION_SERVICE_HAVE_UBUNTU_PLATFORM_HARDWARE_API 
-DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GEOCLUE 
-DCOM_UBUNTU_LOCATION_SERVICE_PROVIDERS_GPS 
-Dubuntu_location_service_connectivity_EXPORTS 
-I/<>/location-service-3.0.0+16.10.20160912/3rd-party 
-I/usr/include/dbus-1.0 -I/usr/lib/x86_64-linux-gnu/dbus-1.0/include 
-I/usr/include/json-c 
-I/<>/location-service-3.0.0+16.10.20160912/include/location_service 
-I/<>/location-service-3.0.0+16.10.20160912/src/location_service 
-I/<>/location-service-3.0.0+16.10.20160912/obj-x86_64-linux-gnu/src/location_service
 -I/usr/include/ubuntu  -g -O2 
-fdebug-prefix-map=/<>/location-service-3.0.0+16.10.20160912=. 
-fstack-protector-strong -Wformat -Werror=format-security -Wdate-time 
-D_FORTIFY_SOURCE=2  -std=c++11 -Wall -fno-strict-aliasing -pedantic -Wextra 
-fPIC -Wno-error=unused-local-typedefs -fPIC   -o 
CMakeFiles/ubuntu-location-service-connectivity.dir/connectivity/wireless_network.cpp.o
 -c 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/connectivity/wireless_network.cpp
  In file included from 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.h:21:0,
   from 
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/sntp_client.cpp:19:
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:57:14:
 error: ‘vector’ in namespace ‘std’ does not name a template type
   std::vector xtra_hosts
^~
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:59:10:
 warning: extra ‘;’ [-Wpedantic]
   };
^
  
/<>/location-service-3.0.0+16.10.20160912/src/location_service/com/ubuntu/location/providers/gps/android_hardware_abstraction_layer.h:66:18:
 error: ‘vector’ in namespace ‘std’ does not name a template type
   virtual std::vector download_xtra_data(const Configuration& 
config) = 0;
^~
  make -f po/CMakeFiles/pofiles_70.dir/build.make 
po/CMakeFiles/pofiles_70.dir/depend

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/location-service/+bug/1640320/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1655724] Re: Should not break systemd in trusty, conflicts with snapd

[Thomas Voß]

I'm assuming that vrruiz added verification-needed accidentally.
Removing it again as the report reads like a success.

** Tags removed: verification-needed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server-lts-xenial in Ubuntu.
https://bugs.launchpad.net/bugs/1655724

Title:
  Should not break systemd in trusty, conflicts with snapd

Status in xorg-server-lts-xenial package in Ubuntu:
  Invalid
Status in xorg-server-lts-xenial source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  * With introduction of snapd/systemd in trusty, it has become impossible to 
install xorg-server-lts-xenial simultaniously with snapd/systemd.
  * In trusty, logind is managed by upstart, and is not restarted on upgrades, 
therefore the protective breaks in xorg-server-lts-xenial is unnecessary in 
trusty only.

  [Testcase]
  * installing snapd, should not remove xorg-server-lts-xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-xenial/+bug/1655724/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1655724] Re: Should not break systemd in trusty, conflicts with snapd

[Thomas Voß]

I verified that the package from -proposed enables installation of
snapd/systemd without any issues. Waiting for qa to give a vote, too,
before setting to verification-done.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg-server-lts-xenial in Ubuntu.
https://bugs.launchpad.net/bugs/1655724

Title:
  Should not break systemd in trusty, conflicts with snapd

Status in xorg-server-lts-xenial package in Ubuntu:
  Invalid
Status in xorg-server-lts-xenial source package in Trusty:
  Fix Committed

Bug description:
  [Impact]
  * With introduction of snapd/systemd in trusty, it has become impossible to 
install xorg-server-lts-xenial simultaniously with snapd/systemd.
  * In trusty, logind is managed by upstart, and is not restarted on upgrades, 
therefore the protective breaks in xorg-server-lts-xenial is unnecessary in 
trusty only.

  [Testcase]
  * installing snapd, should not remove xorg-server-lts-xenial

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/xorg-server-lts-xenial/+bug/1655724/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1630014] Re: GPS is unable to find any position

[Thomas Voß]

No visible satellites in an indoor scenario is certainly possible.
Do you have SIM cards in your phone? Are you actively connected to an AP?

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to location-service in Ubuntu.
https://bugs.launchpad.net/bugs/1630014

Title:
  GPS is unable to find any position

Status in Canonical System Image:
  New
Status in location-service package in Ubuntu:
  New

Bug description:
  Even if you enable tracking position on Aquaris E 4.5, either with
  here drive or just with the GPS on, no position is tracked.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1630014/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1609989] Re: Undefined behavior "member call on null pointer of type 'const struct ResultHolder'"

[Thomas Voß]

** Also affects: gmock (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: gmock (Ubuntu)
   Importance: Undecided => Critical

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtest in Ubuntu.
https://bugs.launchpad.net/bugs/1609989

Title:
  Undefined behavior "member call on null pointer of type 'const struct
  ResultHolder'"

Status in gmock package in Ubuntu:
  New
Status in gtest package in Ubuntu:
  New

Bug description:
  Please see https://github.com/google/googletest/issues/705 for
  details. The respective issue mentions two possible solution:

  [1.] Make sure that commit
  
https://github.com/google/googletest/commit/b5c81098a8ccc25e313ffca56c911200b3591ea0
  is present in the package.

  [2.] Apply the patch mentioned in
  https://github.com/google/googletest/issues/705#issuecomment-235067917.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gmock/+bug/1609989/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1609989] [NEW] Undefined behavior "member call on null pointer of type 'const struct ResultHolder'"

[Thomas Voß]

Public bug reported:

Please see https://github.com/google/googletest/issues/705 for details.
The respective issue mentions two possible solution:

[1.] Make sure that commit
https://github.com/google/googletest/commit/b5c81098a8ccc25e313ffca56c911200b3591ea0
is present in the package.

[2.] Apply the patch mentioned in
https://github.com/google/googletest/issues/705#issuecomment-235067917.

** Affects: gtest (Ubuntu)
 Importance: Critical
 Status: New

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gtest in Ubuntu.
https://bugs.launchpad.net/bugs/1609989

Title:
  Undefined behavior "member call on null pointer of type 'const struct
  ResultHolder'"

Status in gtest package in Ubuntu:
  New

Bug description:
  Please see https://github.com/google/googletest/issues/705 for
  details. The respective issue mentions two possible solution:

  [1.] Make sure that commit
  
https://github.com/google/googletest/commit/b5c81098a8ccc25e313ffca56c911200b3591ea0
  is present in the package.

  [2.] Apply the patch mentioned in
  https://github.com/google/googletest/issues/705#issuecomment-235067917.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/gtest/+bug/1609989/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1591935] Re: audio record works for call audio

[Thomas Voß]

On the trust-store aspect of this: pulseaudio should use the "feature"
field when asking trust-store to verify requests, and use different
enumeration values to distinguish ordinary microphone recording from
voicecall recording. The respective functionality is available from
trust-store today.

Taking the bigger picture into account, I would vote in favor of keeping
the voicecall recording feature enabled under the assumption that the
different recording types are clearly surfaced to the user.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1591935

Title:
  audio record works for call audio

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in trust-store package in Ubuntu:
  Confirmed

Bug description:
  krillin:ubuntu-touch/rc-proposed/bq-aquaris.en,#350

  Install the app 'Recorder' from the Ubuntu Store.

  Confirm it works by opening and making a recording. Note that the app
  requests permission to access the microphone, and you grant this with
  the usual trust store prompt.

  Now move to the phone app, and place a regular phone call. With the
  call active, open Recorder again, and start recording.

  Stop recording after some time, and hang up the call.

  return to the recorder app, and play the recording made during the
  phone call. Audio from both the local microphone and the remote
  handset (Which the user heard during the call) will be present on the
  track.

  It was expected that no audio from the call could be captured by
  applications.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1591935/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1596330] Re: AVRCP not working

[Thomas Voß]

** Changed in: dbus-cpp (Ubuntu)
   Status: New => Confirmed

** Changed in: media-hub (Ubuntu)
   Status: New => Confirmed

** Changed in: dbus-cpp (Ubuntu)
   Importance: Undecided => High

** Changed in: media-hub (Ubuntu)
   Importance: Undecided => High

** Changed in: dbus-cpp (Ubuntu)
 Assignee: (unassigned) => Thomas Voß (thomas-voss)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1596330

Title:
  AVRCP not working

Status in Client Developer Experience:
  New
Status in dbus-cpp package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu:
  Confirmed

Bug description:
  AVRCP is still not working. I've digged a bit into it and it seems the
  reason is that mpris-proxy fails to introspect the MPRIS interface of
  media-hub. The reason for that seems to be that dbus-cpp does not
  correctly reply to GetAll property requests on D-Bus. I'm not entirely
  sure if it's an issue in libdbus-cpp, or wrong usage of it in media-
  hub.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-developer-experience/+bug/1596330/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1524131] Re: /usr/bin/mediaplayer-app:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write

[Thomas Voß]

** Changed in: dbus-cpp (Ubuntu)
 Assignee: (unassigned) => Thomas Voß (thomas-voss)

** Changed in: mediaplayer-app (Ubuntu)
 Assignee: (unassigned) => Thomas Voß (thomas-voss)

** Changed in: dbus-cpp (Ubuntu)
   Importance: Undecided => Critical

** Changed in: dbus-cpp (Ubuntu)
   Status: Confirmed => In Progress

** Changed in: canonical-devices-system-image
   Status: Confirmed => In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1524131

Title:
  /usr/bin/mediaplayer-
  
app:11:__memcpy_neon:std::char_traits:std::basic_streambuf:std::basic_streambuf:std::__ostream_write

Status in Canonical System Image:
  In Progress
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in mediaplayer-app package in Ubuntu:
  Invalid

Bug description:
  Top 3 over the past week on errors.u.c. mediaplayer has not been
  updated for a while and the frequency increased significantly around
  mid-december, probably due to a change in an underlying component
  (gstreamer has been updated on Dec. 12th or it could be the major dbus
  match rules changes as the stacktrace would suggest)

  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding mediaplayer-app.  This problem was most recently seen with
  version 0.20.5+15.04.20150701-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/a649a8d64746c3cce478208950c51611a06323cb
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1524131/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1526877] Re: Dbus errors in the console when closing the music-app

[Thomas Voß]

** Changed in: dbus-cpp (Ubuntu)
   Status: New => Confirmed

** Changed in: dbus-cpp (Ubuntu RTM)
   Status: New => Confirmed

** Changed in: dbus-cpp (Ubuntu)
 Assignee: (unassigned) => Thomas Voß (thomas-voss)

** Changed in: dbus-cpp (Ubuntu RTM)
 Assignee: (unassigned) => Thomas Voß (thomas-voss)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1526877

Title:
  Dbus errors in the console when closing the music-app

Status in Ubuntu Music App:
  New
Status in dbus-cpp package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu:
  New
Status in dbus-cpp package in Ubuntu RTM:
  Confirmed
Status in media-hub package in Ubuntu RTM:
  New

Bug description:
  Due to bug 1434584 being fixed when you swipe to close an application
  the following appears in the log, note the dbus errors, and that I am
  not able to reproduce this on the desktop.

  
  ** Application is now inactive
  Attempted to deliver an event to a non-existent window, ignoring.
  virtual bool QMediaPlaylist::setMediaObject(QMediaObject*)
  void QMediaPlaylistPrivate::syncControls(QMediaPlaylistControl*, 
QMediaPlaylistControl*)
  void AalMediaPlayerService::deletePlaylistControl()
  virtual AalMediaPlaylistProvider::~AalMediaPlaylistProvider()
  void AalMediaPlaylistProvider::disconnect_signals()
  virtual AalMediaPlaylistControl::~AalMediaPlaylistControl()
  void AalMediaPlayerService::deleteMediaPlayerControl()
  void AalMediaPlayerService::destroyPlayerSession()
  PlaybackStatusChanged signal arrived via the bus (Status: 
PlaybackStatus::ready)
  PlaybackStatusChanged signal arrived via the bus (Status: 
PlaybackStatus::stopped)
  OnTrackListReset signal arrived via the bus.
  Attempted to unregister path (path[0] = com path[1] = canonical) which isn't 
registered
  process 6617: arguments to dbus_connection_close() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2935.
  This is normally a bug in some application using the D-Bus library.
  process 6617: arguments to dbus_connection_unref() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2822.
  This is normally a bug in some application using the D-Bus library.
  process 6617: arguments to dbus_connection_unref() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2822.
  This is normally a bug in some application using the D-Bus library.
  process 6617: arguments to dbus_connection_close() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2935.
  This is normally a bug in some application using the D-Bus library.
  process 6617: arguments to dbus_connection_unref() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2822.
  This is normally a bug in some application using the D-Bus library.
  process 6617: arguments to dbus_connection_unref() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2822.
  This is normally a bug in some application using the D-Bus library.
  Sdk-Launcher> Stopping Application
  Sdk-Launcher> The Application exited, cleaning up
  Sdk-Launcher> Finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/music-app/+bug/1526877/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1526877] Re: Dbus errors in the console when closing the music-app

[Thomas Voß]

** Branch linked: lp:~thomas-voss/dbus-cpp/fix-1526877

** Changed in: dbus-cpp (Ubuntu RTM)
   Importance: Undecided => High

** Changed in: dbus-cpp (Ubuntu)
   Importance: Undecided => High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1526877

Title:
  Dbus errors in the console when closing the music-app

Status in Ubuntu Music App:
  New
Status in dbus-cpp package in Ubuntu:
  Confirmed
Status in media-hub package in Ubuntu:
  New
Status in dbus-cpp package in Ubuntu RTM:
  Confirmed
Status in media-hub package in Ubuntu RTM:
  New

Bug description:
  Due to bug 1434584 being fixed when you swipe to close an application
  the following appears in the log, note the dbus errors, and that I am
  not able to reproduce this on the desktop.

  
  ** Application is now inactive
  Attempted to deliver an event to a non-existent window, ignoring.
  virtual bool QMediaPlaylist::setMediaObject(QMediaObject*)
  void QMediaPlaylistPrivate::syncControls(QMediaPlaylistControl*, 
QMediaPlaylistControl*)
  void AalMediaPlayerService::deletePlaylistControl()
  virtual AalMediaPlaylistProvider::~AalMediaPlaylistProvider()
  void AalMediaPlaylistProvider::disconnect_signals()
  virtual AalMediaPlaylistControl::~AalMediaPlaylistControl()
  void AalMediaPlayerService::deleteMediaPlayerControl()
  void AalMediaPlayerService::destroyPlayerSession()
  PlaybackStatusChanged signal arrived via the bus (Status: 
PlaybackStatus::ready)
  PlaybackStatusChanged signal arrived via the bus (Status: 
PlaybackStatus::stopped)
  OnTrackListReset signal arrived via the bus.
  Attempted to unregister path (path[0] = com path[1] = canonical) which isn't 
registered
  process 6617: arguments to dbus_connection_close() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2935.
  This is normally a bug in some application using the D-Bus library.
  process 6617: arguments to dbus_connection_unref() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2822.
  This is normally a bug in some application using the D-Bus library.
  process 6617: arguments to dbus_connection_unref() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2822.
  This is normally a bug in some application using the D-Bus library.
  process 6617: arguments to dbus_connection_close() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2935.
  This is normally a bug in some application using the D-Bus library.
  process 6617: arguments to dbus_connection_unref() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2822.
  This is normally a bug in some application using the D-Bus library.
  process 6617: arguments to dbus_connection_unref() were incorrect, assertion 
"connection->generation == _dbus_current_generation" failed in file 
../../dbus/dbus-connection.c line 2822.
  This is normally a bug in some application using the D-Bus library.
  Sdk-Launcher> Stopping Application
  Sdk-Launcher> The Application exited, cleaning up
  Sdk-Launcher> Finished

To manage notifications about this bug go to:
https://bugs.launchpad.net/music-app/+bug/1526877/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Thomas Voß]

** Changed in: dbus-cpp (Ubuntu)
   Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Fix Released
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Triaged
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released
Status in location-service package in Ubuntu RTM:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu RTM:
  Fix Released

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Thomas Voß]

Thanks for the graphs. One thing that stands out is the time that the
system stays active when occasionally waking up from deep sleep (right
hand side of the graph).
Do you have the raw data producing those graphs handy?

Thanks,

  Thomas

On Wed, Dec 9, 2015 at 1:23 AM, Selene Scriven
 wrote:
> Is it possible that this fix might cause a phone to wake up more often,
> or to stay awake longer?  I'm seeing weird idle power behavior ever
> since this fix landed in krillin rc-proposed 196.
>
> Before: ~9 mA
> http://people.canonical.com/~platform-qa/power-results/2015-12-08_03:19:30-krillin-195-power_usage_idle/graph.png
>
> After: ~35 mA
> http://people.canonical.com/~platform-qa/power-results/2015-12-08_07:36:16-krillin-196-power_usage_idle/graph.png
>
> Here's the commit log for 196:
>
> http://people.canonical.com/~lzemczak/landing-team/ubuntu-touch/rc-
> proposed/196.commitlog
>
> Arale results look fine.  I don't know why krillin is different, but I'm
> only seeing this behavior on krillin when wifi is connected...  and this
> bug fix is a likely suspect.  I don't see additional forks or crashes in
> the test logs, which suggests the issue is probably caused by a long-
> running process.
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1480877
>
> Title:
>   Access points' "PropertiesChanged" dbus signals freeze UI on mobile
>   devices
>
> Status in Canonical System Image:
>   Fix Committed
> Status in Unity 8:
>   New
> Status in dbus-cpp package in Ubuntu:
>   In Progress
> Status in network-manager package in Ubuntu:
>   Incomplete
> Status in qtbase-opensource-src package in Ubuntu:
>   Fix Committed
> Status in dbus-cpp package in Ubuntu RTM:
>   Fix Released
> Status in location-service package in Ubuntu RTM:
>   Fix Released
> Status in network-manager package in Ubuntu RTM:
>   Incomplete
>
> Bug description:
>   Krillin, rc-proposed, r83
>
>
>   DESCRIPTION:
>   I've been trying to track down the cause of the occasional UI freezes on my 
> Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
> get a burst of "PropertiesChanged" signals in dbus-monitor
>
>   Here's a log of what's shown in dbus-monitor:
>   http://pastebin.ubuntu.com/11992322/
>
>   I'd guess the problem is in the code that actually catches the signals
>   and acts accordingly.
>
>   HOW TO REPRODUCE:
>   1) Move to a place where many wifi hotspots are available
>   2) Connect the device via USB and run "phablet-shell" and then 
> "dbus-monitor"
>   3) Use the device while keeping an eye on dbus-monitor output
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Fix Committed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Fix Committed
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released
Status in location-service package in Ubuntu RTM:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Incomplete

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Thomas Voß]

Silo 26 is now complete.

On Mon, Nov 23, 2015 at 4:47 PM, Thomas Voß <thomas.v...@canonical.com> wrote:
> Quick update on silo 26: I'm rebuilding location-service to account
> for a recent landing.
> The one blocking issue is mediascanner2, which requires a rebuild,
> too. It is however enabled for dual-landing
> to both vivid and xenial, and we cannot easily do a vivid+o landing
> with it right now. I'm working on the resolving that issue,
> but it will likely take a day or two to complete.
>
> On Mon, Nov 23, 2015 at 3:49 PM, Michael Terry
> <michael.te...@canonical.com> wrote:
>> I tested silo 26 + libqt5network5 from Tony's PPA and did my normal
>> routine of walking out of range of my home network.
>>
>> It seems much better.  dbus-daemon CPU usage is down (only ~30% for a
>> few seconds after initial switch to 3G and ~15% during scans after).
>>
>> But more importantly, stuttering is much better.  Only a couple tiny
>> stutters on initial switch.  And none during scans.  I'm +100 on trying
>> to land this.
>>
>> (My test was on a relatively-recently-rebooted phone, so maybe not the
>> ideal test.  I'll try again later after a while of uptime to double
>> confirm the results, but this looks good.  If I don't post again, assume
>> it worked great.)
>>
>> --
>> You received this bug notification because you are a bug assignee.
>> https://bugs.launchpad.net/bugs/1480877
>>
>> Title:
>>   Access points' "PropertiesChanged" dbus signals freeze UI on mobile
>>   devices
>>
>> Status in Canonical System Image:
>>   Confirmed
>> Status in Unity 8:
>>   New
>> Status in dbus-cpp package in Ubuntu:
>>   In Progress
>> Status in indicator-network package in Ubuntu:
>>   Incomplete
>> Status in network-manager package in Ubuntu:
>>   Incomplete
>> Status in qtbase-opensource-src package in Ubuntu:
>>   In Progress
>> Status in buteo-syncfw package in Ubuntu RTM:
>>   New
>> Status in location-service package in Ubuntu RTM:
>>   In Progress
>> Status in maliit-framework package in Ubuntu RTM:
>>   New
>> Status in network-manager package in Ubuntu RTM:
>>   Incomplete
>> Status in sync-monitor package in Ubuntu RTM:
>>   New
>>
>> Bug description:
>>   Krillin, rc-proposed, r83
>>
>>
>>   DESCRIPTION:
>>   I've been trying to track down the cause of the occasional UI freezes on 
>> my Krillin device, and I noticed that whenever the UI freezes for 2-4 
>> seconds, I get a burst of "PropertiesChanged" signals in dbus-monitor
>>
>>   Here's a log of what's shown in dbus-monitor:
>>   http://pastebin.ubuntu.com/11992322/
>>
>>   I'd guess the problem is in the code that actually catches the signals
>>   and acts accordingly.
>>
>>   HOW TO REPRODUCE:
>>   1) Move to a place where many wifi hotspots are available
>>   2) Connect the device via USB and run "phablet-shell" and then 
>> "dbus-monitor"
>>   3) Use the device while keeping an eye on dbus-monitor output
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in buteo-syncfw package in Ubuntu RTM:
  New
Status in location-service package in Ubuntu RTM:
  In Progress
Status in maliit-framework package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in sync-monitor package in Ubuntu RTM:
  New

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

Re: [Desktop-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Thomas Voß]

Quick update on silo 26: I'm rebuilding location-service to account
for a recent landing.
The one blocking issue is mediascanner2, which requires a rebuild,
too. It is however enabled for dual-landing
to both vivid and xenial, and we cannot easily do a vivid+o landing
with it right now. I'm working on the resolving that issue,
but it will likely take a day or two to complete.

On Mon, Nov 23, 2015 at 3:49 PM, Michael Terry
 wrote:
> I tested silo 26 + libqt5network5 from Tony's PPA and did my normal
> routine of walking out of range of my home network.
>
> It seems much better.  dbus-daemon CPU usage is down (only ~30% for a
> few seconds after initial switch to 3G and ~15% during scans after).
>
> But more importantly, stuttering is much better.  Only a couple tiny
> stutters on initial switch.  And none during scans.  I'm +100 on trying
> to land this.
>
> (My test was on a relatively-recently-rebooted phone, so maybe not the
> ideal test.  I'll try again later after a while of uptime to double
> confirm the results, but this looks good.  If I don't post again, assume
> it worked great.)
>
> --
> You received this bug notification because you are a bug assignee.
> https://bugs.launchpad.net/bugs/1480877
>
> Title:
>   Access points' "PropertiesChanged" dbus signals freeze UI on mobile
>   devices
>
> Status in Canonical System Image:
>   Confirmed
> Status in Unity 8:
>   New
> Status in dbus-cpp package in Ubuntu:
>   In Progress
> Status in indicator-network package in Ubuntu:
>   Incomplete
> Status in network-manager package in Ubuntu:
>   Incomplete
> Status in qtbase-opensource-src package in Ubuntu:
>   In Progress
> Status in buteo-syncfw package in Ubuntu RTM:
>   New
> Status in location-service package in Ubuntu RTM:
>   In Progress
> Status in maliit-framework package in Ubuntu RTM:
>   New
> Status in network-manager package in Ubuntu RTM:
>   Incomplete
> Status in sync-monitor package in Ubuntu RTM:
>   New
>
> Bug description:
>   Krillin, rc-proposed, r83
>
>
>   DESCRIPTION:
>   I've been trying to track down the cause of the occasional UI freezes on my 
> Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
> get a burst of "PropertiesChanged" signals in dbus-monitor
>
>   Here's a log of what's shown in dbus-monitor:
>   http://pastebin.ubuntu.com/11992322/
>
>   I'd guess the problem is in the code that actually catches the signals
>   and acts accordingly.
>
>   HOW TO REPRODUCE:
>   1) Move to a place where many wifi hotspots are available
>   2) Connect the device via USB and run "phablet-shell" and then 
> "dbus-monitor"
>   3) Use the device while keeping an eye on dbus-monitor output
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  In Progress
Status in buteo-syncfw package in Ubuntu RTM:
  New
Status in location-service package in Ubuntu RTM:
  In Progress
Status in maliit-framework package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in sync-monitor package in Ubuntu RTM:
  New

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Thomas Voß]

** Changed in: location-service (Ubuntu RTM)
   Status: Triaged => In Progress

** Changed in: location-service (Ubuntu RTM)
 Assignee: Scott Sweeny (ssweeny) => Thomas Voß (thomas-voss)

** Branch linked: lp:~thomas-voss/location-service/fix-match-rule-leak

** Also affects: dbus-cpp (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: dbus-cpp (Ubuntu)
   Importance: Undecided => High

** Changed in: dbus-cpp (Ubuntu)
   Status: New => In Progress

** Changed in: dbus-cpp (Ubuntu)
 Assignee: (unassigned) => Thomas Voß (thomas-voss)

** Branch linked: lp:~thomas-voss/dbus-cpp/fix-signal-subscriptions

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in Unity 8:
  New
Status in dbus-cpp package in Ubuntu:
  In Progress
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in qtbase-opensource-src package in Ubuntu:
  Confirmed
Status in buteo-syncfw package in Ubuntu RTM:
  New
Status in location-service package in Ubuntu RTM:
  In Progress
Status in maliit-framework package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in sync-monitor package in Ubuntu RTM:
  New

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Thomas Voß]

** Changed in: location-service (Ubuntu RTM)
   Status: New => Triaged

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Confirmed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Incomplete
Status in buteo-syncfw package in Ubuntu RTM:
  New
Status in location-service package in Ubuntu RTM:
  Triaged
Status in maliit-framework package in Ubuntu RTM:
  New
Status in network-manager package in Ubuntu RTM:
  Incomplete
Status in sync-monitor package in Ubuntu RTM:
  New
Status in unity8 package in Ubuntu RTM:
  New

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1480877] Re: Access points' "PropertiesChanged" dbus signals freeze UI on mobile devices

[Thomas Voß]

** No longer affects: location-service (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1480877

Title:
  Access points' "PropertiesChanged" dbus signals freeze UI on mobile
  devices

Status in Canonical System Image:
  Fix Committed
Status in indicator-network package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Fix Released

Bug description:
  Krillin, rc-proposed, r83

  
  DESCRIPTION:
  I've been trying to track down the cause of the occasional UI freezes on my 
Krillin device, and I noticed that whenever the UI freezes for 2-4 seconds, I 
get a burst of "PropertiesChanged" signals in dbus-monitor

  Here's a log of what's shown in dbus-monitor:
  http://pastebin.ubuntu.com/11992322/

  I'd guess the problem is in the code that actually catches the signals
  and acts accordingly.

  HOW TO REPRODUCE: 
  1) Move to a place where many wifi hotspots are available
  2) Connect the device via USB and run "phablet-shell" and then "dbus-monitor"
  3) Use the device while keeping an eye on dbus-monitor output

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1480877/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1487129] Re: camera-app mic permission item blank

[Thomas Voß]

Interestingly, the entry for the CameraService is correct and
constitutes a valid App id. However, the entry for the microphone is not
a valid app id but seems to come from a service that runs under an app-
armor profile qtubuntu-camera. I think we might need to patch the
respective service, too, to enable trust integration.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1487129

Title:
  camera-app mic permission item blank

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  Working through camera/mic trust issues, discovering that the camera-
  app's mic item under Other app access is blank, will attach a
  screenie.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487129/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1487129] Re: camera-app mic permission item blank

[Thomas Voß]

@mpt: Sure, let's first iron out the actual underlying issues though.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pulseaudio in Ubuntu.
https://bugs.launchpad.net/bugs/1487129

Title:
  camera-app mic permission item blank

Status in Canonical System Image:
  Confirmed
Status in pulseaudio package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Invalid

Bug description:
  Working through camera/mic trust issues, discovering that the camera-
  app's mic item under Other app access is blank, will attach a
  screenie.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1487129/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1481279] Re: GCC5: Phone restarts if you click on anything in the first page of welcome wizard

[Thomas Voß]

** Also affects: dbus-cpp (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: dbus-cpp (Ubuntu)
 Assignee: (unassigned) = Thomas Voß (thomas-voss)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1481279

Title:
  GCC5: Phone restarts if you click on anything in the first page of
  welcome wizard

Status in dbus-cpp package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  Invalid

Bug description:
  STEPS:
  1. Install the latest gcc5 test image
  2. Get to the welcome wizard
  3. Tap the language drop down
  4. Reboots
  5. Tap the Continue Button
  6. Reboots

  EXPECTED:
  I expect the welcome wizard to work the same as it does on vivid

  ACTUAL:
  Any option you tap on as soon as the signal is received it reboots the phone.

  VERSIONS:
  Image 3

  Logs to follow once I can strip them out of the device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1481279/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1481279] Re: GCC5: Phone restarts if you click on anything in the first page of welcome wizard

[Thomas Voß]

** No longer affects: unity8 (Ubuntu)

** No longer affects: dbus-cpp (Ubuntu)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1481279

Title:
  GCC5: Phone restarts if you click on anything in the first page of
  welcome wizard

Status in platform-api package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  1. Install the latest gcc5 test image
  2. Get to the welcome wizard
  3. Tap the language drop down
  4. Reboots
  5. Tap the Continue Button
  6. Reboots

  EXPECTED:
  I expect the welcome wizard to work the same as it does on vivid

  ACTUAL:
  Any option you tap on as soon as the signal is received it reboots the phone.

  VERSIONS:
  Image 3

  Logs to follow once I can strip them out of the device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/platform-api/+bug/1481279/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1481279] Re: GCC5: Phone restarts if you click on anything in the first page of welcome wizard

[Thomas Voß]

** Changed in: unity8 (Ubuntu)
   Status: New = Invalid

** Also affects: platform-api (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: platform-api (Ubuntu)
   Status: New = In Progress

** Changed in: platform-api (Ubuntu)
   Importance: Undecided = Critical

** Changed in: platform-api (Ubuntu)
 Assignee: (unassigned) = Thomas Voß (thomas-voss)

** Changed in: dbus-cpp (Ubuntu)
   Status: New = Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1481279

Title:
  GCC5: Phone restarts if you click on anything in the first page of
  welcome wizard

Status in platform-api package in Ubuntu:
  In Progress

Bug description:
  STEPS:
  1. Install the latest gcc5 test image
  2. Get to the welcome wizard
  3. Tap the language drop down
  4. Reboots
  5. Tap the Continue Button
  6. Reboots

  EXPECTED:
  I expect the welcome wizard to work the same as it does on vivid

  ACTUAL:
  Any option you tap on as soon as the signal is received it reboots the phone.

  VERSIONS:
  Image 3

  Logs to follow once I can strip them out of the device.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/platform-api/+bug/1481279/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1452322] Re: please drop build-dependency on g++-4.9

[Thomas Voß]

** Changed in: dbus-cpp (Ubuntu)
 Assignee: (unassigned) = Thomas Voß (thomas-voss)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1452322

Title:
  please drop build-dependency on g++-4.9

Status in dbus-cpp package in Ubuntu:
  Confirmed

Bug description:
  The dbus-cpp package currently has a build-dependency on g++-4.9. This
  build-dependency is present because of the recommendations on
  https://wiki.ubuntu.com/cpp-11 about handling of C++11.

  The C++11 ABI has now stabilized in gcc as of gcc 5; however, before
  we can switch to gcc 5, we first need to be able to do rebuild tests
  of the archive against this compiler.

  To facilitate this, please drop the build-dependency on g++-4.9 from
  the package in wily. 4.9 will remain the default until all transition
  issues have been identified, so there is no risk of accidental ABI
  breakage here anymore.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1452322/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP (timeout for the AP to be removed is too big, ~6min)

[Thomas Voß]

I investigated into the Android approach, and it turns out that they
solely rely on the last scan results to populate the settings panel.
Please see
https://docs.google.com/document/d/1DTvgpnJ37PvdHt_L65xtj4wdCnBfo8kAaUcBIp5c1U4/edit
for a summary together with links to the relevant Java code.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1425172

Title:
  Network indicator lists the non-exist AP (timeout for the AP to be
  removed is too big, ~6min)

Status in the base for Ubuntu mobile products:
  Confirmed
Status in indicator-network package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in ubuntu-system-settings package in Ubuntu:
  Incomplete
Status in network-manager package in Ubuntu RTM:
  Confirmed

Bug description:
  Summary: Network indicator lists the non-exist AP
  Steps to reproduce:
  1. Boot to system
  2. Scroll down the Network indicator
  3. It lists about 10 AP (In Taipei office)
  4. Go to another place and check network indicator again

  Expected Result:
  It should not list non-exist AP and only show available AP

  Actual Result:
  It shows about 12 AP on the screen but only two are real AP for connecting, 
and others 10 are from last list.

  This is reproducible on mako/krillin on both RTM and vivid.

  The main issue is that the timeout for the AP to be removed from the
  known AP list is too big when comparing with other phones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1396985] Re: Dbus-c++ leaks memory

[Thomas Voß]

** Changed in: dbus-cpp
   Status: In Progress = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1396985

Title:
  Dbus-c++ leaks memory

Status in the base for Ubuntu mobile products:
  Fix Released
Status in DBus C++:
  Fix Released
Status in dbus-cpp package in Ubuntu:
  Fix Released

Bug description:
  The sample program that comes with dbus-cpp (and thus presumably all
  clients of dbus-cpp) leaks memory quite badly. To test do this:

  valgrind --tool=massif --trace-children=yes
  examples/benchmark/benchmark

  Then view the result with massif-viewer. The image is attached and
  shows that memory consumption keeps on increasing all the time and
  never drops. Presumably because dbus-cpp is not properly releasing
  resources in libdbus-1.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1396985/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1394204] Re: dbus daemon spinning with NM AP properties change event

[Thomas Voß]

** No longer affects: location-service

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1394204

Title:
  dbus daemon spinning with NM AP properties change event

Status in the base for Ubuntu mobile products:
  Fix Released
Status in network-manager package in Ubuntu:
  Invalid
Status in location-service package in Ubuntu RTM:
  Fix Released
Status in network-manager package in Ubuntu RTM:
  Invalid

Bug description:
  I am consistently seeing this in the Bluefin office this week
  Mako running 133

  Phone gets warm in pocket, wake up the phone and attach
  top shows dbus-daemon at 100%+ cpu and network-manager next at 10-20%
  It never quiets own, at least not for over 5 mins

  3g data is turned off
  Cellular is roaming to local carrier fwiw
  Seems to happen whenever I leave the AP coverage, whether I return or not

  Reproducing the issue: The problem is easily reproducible when forcing NM to 
roam between multiple access points and never quite finishing the association 
to one AP. At home, I reproduce by
  roaming between different floors, where each floor has got its own WiFi. Any 
sufficiently complex office WiFi setup should trigger it, too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1394204/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1361642] Re: DBus.Properties.Get/Set having a hardcoded default timeout of 1000ms

[Thomas Voß]

** Changed in: dbus-cpp
   Status: Confirmed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1361642

Title:
  DBus.Properties.Get/Set having a hardcoded default timeout of 1000ms

Status in DBus C++:
  Fix Released
Status in dbus-cpp package in Ubuntu:
  Fix Released
Status in dbus-cpp package in Ubuntu RTM:
  Fix Released

Bug description:
  This causes issues such as found here:

  https://code.launchpad.net/~jpakkane/indicator-
  network/grace/+merge/232194

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-cpp/+bug/1361642/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1425172] Re: Network indicator lists the non-exist AP

[Thomas Voß]

May well be a duplicate of https://bugs.launchpad.net/ubuntu/+source
/network-manager/+bug/1427205

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1425172

Title:
  Network indicator lists the non-exist AP

Status in the base for Ubuntu mobile products:
  Confirmed
Status in network-manager package in Ubuntu:
  Confirmed
Status in network-manager package in Ubuntu RTM:
  Confirmed

Bug description:
  Summary: Network indicator lists the non-exist AP
  Steps to reproduce:
  1. Boot to system
  2. Scroll down the Network indicator
  3. It lists about 10 AP (In Taipei office)
  4. Go to another place and check network indicator again

  Expected Result:
  It should not list non-exist AP and only show available AP

  Actual Result:
  It shows about 12 AP on the screen but only two are real AP for connecting, 
and others 10 are from last list.

  This is reproducible on mako/krillin on both RTM and vivid.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1425172/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1358918] Re: ubuntu-location-serviced cpu usage spikes to 100% occasionally

[Thomas Voß]

This should be fixed with the latest images Feel free to reopen if you
manage to reproduce.

** Changed in: dbus-cpp (Ubuntu)
   Status: Confirmed = Fix Released

** Changed in: location-service (Ubuntu)
   Status: Confirmed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1358918

Title:
  ubuntu-location-serviced cpu usage spikes to 100% occasionally

Status in dbus-cpp package in Ubuntu:
  Fix Released
Status in location-service package in Ubuntu:
  Fix Released

Bug description:
  Occasionally, users report the location service daemon CPU usage to
  spike and occupy an entire core of the system. Up until now, we have
  no way of reliably reproducing the issue. If you encounter it, please
  do the following:

* Report the output of /system/bin/logcat on this bug
* If possible, attach to the location service daemon process with:
   * sudo gdb -p ${PID_OF_LOCATION_SERVICE_DAEMON}
   * Call generate-core-file inside gdb
   * Attach the resuling core.${PID_OF_LOCATION_SERVICE_DAEMON} to this 
bug report

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1358918/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1394204] Re: dbus daemon spinning with NM AP properties change event

[Thomas Voß]

I tracked down the root cause to the location service reacting to
changes to the PrimaryConnection property of
org.freedesktop.NetworkManager by reaching out to all devices associated
with the primary connection, and querying their properties, both for
wifi devices and cross-referencing to Ofono for modem devices. This
behavior of not relying on cached values causes excessive traffic on the
bus. The branch attached to this bug mitigates the issue by:

  (1.) Relying on the cached devices for querying device properties. This is 
sufficient, as the cache is always consistent in this particular scenario.
  (2.) Not explicitly reacting to modem state changes coming in via Ofono but 
instead only reacting to changes to the PrimaryConnection property of 
NetworkManager.

** Branch linked: lp:~thomas-voss/location-service/fix-1394204

** Description changed:

  I am consistently seeing this in the Bluefin office this week
  Mako running 133
  
  Phone gets warm in pocket, wake up the phone and attach
  top shows dbus-daemon at 100%+ cpu and network-manager next at 10-20%
  It never quiets own, at least not for over 5 mins
  
  3g data is turned off
  Cellular is roaming to local carrier fwiw
  Seems to happen whenever I leave the AP coverage, whether I return or not
+ 
+ TEST CASE: The problem is easily reproducible when forcing NM to roam between 
multiple access points and never quite finishing the association to one AP. At 
home, I reproduce by  
+ roaming between different floors, where each floor has got its own WiFi. Any 
sufficiently complex office WiFi setup should trigger it, too.

** Description changed:

  I am consistently seeing this in the Bluefin office this week
  Mako running 133
  
  Phone gets warm in pocket, wake up the phone and attach
  top shows dbus-daemon at 100%+ cpu and network-manager next at 10-20%
  It never quiets own, at least not for over 5 mins
  
  3g data is turned off
  Cellular is roaming to local carrier fwiw
  Seems to happen whenever I leave the AP coverage, whether I return or not
  
- TEST CASE: The problem is easily reproducible when forcing NM to roam between 
multiple access points and never quite finishing the association to one AP. At 
home, I reproduce by  
+ Reproducing the issue: The problem is easily reproducible when forcing NM to 
roam between multiple access points and never quite finishing the association 
to one AP. At home, I reproduce by
  roaming between different floors, where each floor has got its own WiFi. Any 
sufficiently complex office WiFi setup should trigger it, too.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1394204

Title:
  dbus daemon spinning with NM AP properties change event

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Location Service:
  New
Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu RTM:
  New

Bug description:
  I am consistently seeing this in the Bluefin office this week
  Mako running 133

  Phone gets warm in pocket, wake up the phone and attach
  top shows dbus-daemon at 100%+ cpu and network-manager next at 10-20%
  It never quiets own, at least not for over 5 mins

  3g data is turned off
  Cellular is roaming to local carrier fwiw
  Seems to happen whenever I leave the AP coverage, whether I return or not

  Reproducing the issue: The problem is easily reproducible when forcing NM to 
roam between multiple access points and never quite finishing the association 
to one AP. At home, I reproduce by
  roaming between different floors, where each floor has got its own WiFi. Any 
sufficiently complex office WiFi setup should trigger it, too.

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1394204/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1394204] Re: dbus daemon spinning with NM AP properties change event

[Thomas Voß]

** Also affects: location-service
   Importance: Undecided
   Status: New

** Changed in: location-service
   Importance: Undecided = Critical

** Changed in: location-service
 Assignee: (unassigned) = Thomas Voß (thomas-voss)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager in Ubuntu.
https://bugs.launchpad.net/bugs/1394204

Title:
  dbus daemon spinning with NM AP properties change event

Status in the base for Ubuntu mobile products:
  Confirmed
Status in Location Service:
  New
Status in network-manager package in Ubuntu:
  In Progress
Status in network-manager package in Ubuntu RTM:
  New

Bug description:
  I am consistently seeing this in the Bluefin office this week
  Mako running 133

  Phone gets warm in pocket, wake up the phone and attach
  top shows dbus-daemon at 100%+ cpu and network-manager next at 10-20%
  It never quiets own, at least not for over 5 mins

  3g data is turned off
  Cellular is roaming to local carrier fwiw
  Seems to happen whenever I leave the AP coverage, whether I return or not

To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1394204/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1390618] Re: Uniy8 crashed when creating a wireless connection with an access point

[Thomas Voß]

Thanks for the report. The issue arises when trying to communicate to
the dbus daemon in a dtor, and I can easily make that call exception
safe. However, that specific call failing is concerning, and we should
further investigate why removing a match rule apparently fails (probably
times out).

** Changed in: dbus-cpp (Ubuntu)
   Importance: Undecided = Critical

** Changed in: dbus-cpp (Ubuntu)
   Status: New = In Progress

** Changed in: dbus-cpp (Ubuntu)
 Assignee: (unassigned) = Thomas Voß (thomas-voss)

** Branch linked: lp:~thomas-voss/dbus-cpp/ensure-Signal-for-void-dtor-
is-exception-safe

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1390618

Title:
  Uniy8 crashed when creating a wireless connection with an access point

Status in “dbus-cpp” package in Ubuntu:
  In Progress
Status in “media-hub” package in Ubuntu:
  New
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  current build number: 11
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2014-11-07 19:25:24
  version version: 11
  version ubuntu: 20141106.1
  version device: 20141106
  version custom: 20141106.1

  Had system-settings opened in order to verify for updates, but noticed
  that I didn't have any valid wireless connection, so when I tried to
  connect with my access point, unity8 crashed completely. This happened
  after adding the password and hitting 'Connect'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1390618/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1390618] Re: Uniy8 crashed when creating a wireless connection with an access point

[Thomas Voß]

** Branch linked: lp:~thomas-voss/media-hub/bump-build-dep

** Changed in: media-hub (Ubuntu)
   Status: New = Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1390618

Title:
  Uniy8 crashed when creating a wireless connection with an access point

Status in “dbus-cpp” package in Ubuntu:
  In Progress
Status in “media-hub” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  current build number: 11
  device name: mako
  channel: ubuntu-touch/vivid-proposed
  last update: 2014-11-07 19:25:24
  version version: 11
  version ubuntu: 20141106.1
  version device: 20141106
  version custom: 20141106.1

  Had system-settings opened in order to verify for updates, but noticed
  that I didn't have any valid wireless connection, so when I tried to
  connect with my access point, unity8 crashed completely. This happened
  after adding the password and hitting 'Connect'.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1390618/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Ass

[Thomas Voß]

** Changed in: dbus-cpp (Ubuntu)
   Status: In Progress = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1382595

Title:
  [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-
  network-service:indicator-network-service: pthread_mutex_lock.c:80:
  __pthread_mutex_lock: Assertion `mutex-__data.__owner == 0' failed.

Status in DBus C++:
  Fix Released
Status in “dbus-cpp” package in Ubuntu:
  Fix Released
Status in “indicator-network” package in Ubuntu:
  Invalid
Status in “location-service” package in Ubuntu:
  Invalid
Status in “dbus-cpp” package in Ubuntu RTM:
  Fix Released
Status in “indicator-network” package in Ubuntu RTM:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding indicator-network.  This problem was most recently seen with
  version 0.5.1+14.10.20141015-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/ecc14b5d54f3e0a0f1720cad0c623f81c8a16988
  contains more details.

  steps to reproduce: (need to trigger race condition)
  1. pull down network indicator
  2. toggle flight mode on and off quickly a few times
  3. click sim card 1 and 2
  4. toggle flight mode
  5. swipe up close indicators
  6. repeat steps 1-5 until crash occurs

  expected results:
  no crash happens

  actual results:
  Bluetooth indicator blinks (appear and disappear) in indicator bar at top of 
screen, and network indicator crashes. 

  additional info:
  eventually the bluetooth indicator appears stable in the indicators at the 
top of the screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1380736] Re: showing notification right after boot causes unity8 crash

[Thomas Voß]

*** This bug is a duplicate of bug 1387959 ***
https://bugs.launchpad.net/bugs/1387959

** This bug has been marked a duplicate of bug 1387959
   [TOPBLOCKER] unity8 crash in image krillin rtm 139

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1380736

Title:
  showing notification right after boot causes unity8 crash

Status in Network Menu:
  Invalid
Status in “dbus-cpp” package in Ubuntu:
  Invalid
Status in “media-hub” package in Ubuntu:
  Invalid
Status in “qtubuntu-media” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Invalid
Status in “qtubuntu-media” package in Ubuntu RTM:
  Fix Released

Bug description:
  STEPS:
  1. Install a new image (Apparently it works with just re-running the wizard)
  2. While the dash is empty drag down the network indicator
  3. Click on the first unlock sim button
  4. Type in the unlock code and hit the tick
  5. System locks up

  EXPECTED:
  I expect the lock you unlock the sim and change back to the indicator

  ACTUAL:
  The system hard locks nothing works.  In the end you are forced to hard 
shutdown the phone by pressing and holding the power button till the phone 
powers down.

  Booting the Phone back up after this and everthing works as expected.
  Also waiting on the dash to fully load and fill with apps and then unlocking 
works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-network/+bug/1380736/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1380848] Re: Apps and services use large amount of CPU after unity8 resets

[Thomas Voß]

We should assign this bug to an overarching component/project as
multiple independent services (media-hub, location-service, dbus-daemon)
are affected.

However, one idea that came to my mind: It might be that a spurious
posix signal is causing these issues, probably a SIGHUP somewhere,
arising on a thread that the respective signal is not blocked on. I will
keep on investigating into that direction.

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1380848

Title:
  Apps and services use large amount of CPU after unity8 resets

Status in Media Hub:
  Triaged
Status in “dbus-cpp” package in Ubuntu:
  New

Bug description:
  I noticed that media-hub-service can get into a state where it uses a
  large amount of CPU.

  Steps to reproduce
  1) Start music-app
  2) Play music
  3) Pause music
  4) Close the music-app
  5) $ pkill unity8 (to emulate unity crashing a resetting)

  Notice that media-hub-service is now using a large amount of CPU, note
  this [0] is the media-hub.log at the time.

  The device has to be reset to get the CPU usage back to normal.

  0 - http://pastebin.ubuntu.com/8553411/

To manage notifications about this bug go to:
https://bugs.launchpad.net/media-hub/+bug/1380848/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1386803] Re: [TOPBLOCKER] unity8 crashing a lot since image #126

[Thomas Voß]

** Changed in: qtubuntu-media (Ubuntu)
   Importance: Undecided = Critical

** Branch linked: lp:~thomas-voss/qtubuntu-media/disconnect-from-
playback-status-changed-signal-on-destruction

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1386803

Title:
  [TOPBLOCKER] unity8 crashing a lot since image #126

Status in “dbus-cpp” package in Ubuntu:
  Fix Released
Status in “qtubuntu-media” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  Opinion
Status in “media-hub” package in Ubuntu RTM:
  Fix Released

Bug description:
  Since RTM image #126 was released on friday, most users have been
  reporting frequent unity8 crashes. Some scenarios where this commonly
  happen appear to be:

  - Unlocking SIM cards for the first time
  - Tapping on snap notifications when receiving an SMS

  A lot of crashes are also observed during automated image testing.

  ProblemType: Bug
  DistroRelease: Ubuntu RTM 14.09
  Package: unity8 8.00+14.10.20141017-0ubuntu1 [origin: unknown]
  Uname: Linux 3.4.67 armv7l
  ApportVersion: 2.14.7-0ubuntu8
  Architecture: armhf
  Date: Tue Oct 28 17:20:40 2014
  InstallationDate: Installed on 2014-10-28 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20141028-030205)
  SourcePackage: unity8
  UpgradeStatus: No upgrade log present (probably fresh install)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1386803/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Ass

[Thomas Voß]

** Changed in: dbus-cpp
   Status: In Progress = Fix Released

** Changed in: dbus-cpp (Ubuntu RTM)
   Status: In Progress = Fix Released

** Changed in: indicator-network (Ubuntu RTM)
   Status: In Progress = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1382595

Title:
  [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-
  network-service:indicator-network-service: pthread_mutex_lock.c:80:
  __pthread_mutex_lock: Assertion `mutex-__data.__owner == 0' failed.

Status in DBus C++:
  Fix Released
Status in “dbus-cpp” package in Ubuntu:
  In Progress
Status in “indicator-network” package in Ubuntu:
  In Progress
Status in “location-service” package in Ubuntu:
  In Progress
Status in “dbus-cpp” package in Ubuntu RTM:
  Fix Released
Status in “indicator-network” package in Ubuntu RTM:
  Fix Released

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding indicator-network.  This problem was most recently seen with
  version 0.5.1+14.10.20141015-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/ecc14b5d54f3e0a0f1720cad0c623f81c8a16988
  contains more details.

  steps to reproduce: (need to trigger race condition)
  1. pull down network indicator
  2. toggle flight mode on and off quickly a few times
  3. click sim card 1 and 2
  4. toggle flight mode
  5. swipe up close indicators
  6. repeat steps 1-5 until crash occurs

  expected results:
  no crash happens

  actual results:
  Bluetooth indicator blinks (appear and disappear) in indicator bar at top of 
screen, and network indicator crashes. 

  additional info:
  eventually the bluetooth indicator appears stable in the indicators at the 
top of the screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1380848] Re: Apps and services use large amount of CPU after unity8 resets

[Thomas Voß]

I will try to come up with a distilled down test case illustrating that
libdbus-cpp is not the cause but a symptom of the issue. Point being
that it certainly shows up in the stack traces, but it sits waiting in
all of them (specifically for the system settings crash).

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1380848

Title:
  Apps and services use large amount of CPU after unity8 resets

Status in Media Hub:
  Triaged
Status in “dbus-cpp” package in Ubuntu:
  New

Bug description:
  I noticed that media-hub-service can get into a state where it uses a
  large amount of CPU.

  Steps to reproduce
  1) Start music-app
  2) Play music
  3) Pause music
  4) Close the music-app
  5) $ pkill unity8 (to emulate unity crashing a resetting)

  Notice that media-hub-service is now using a large amount of CPU, note
  this [0] is the media-hub.log at the time.

  The device has to be reset to get the CPU usage back to normal.

  0 - http://pastebin.ubuntu.com/8553411/

To manage notifications about this bug go to:
https://bugs.launchpad.net/media-hub/+bug/1380848/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Ass

[Thomas Voß]

** Changed in: dbus-cpp
   Status: Confirmed = In Progress

** Changed in: dbus-cpp (Ubuntu)
   Status: Confirmed = In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1382595

Title:
  [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-
  network-service:indicator-network-service: pthread_mutex_lock.c:80:
  __pthread_mutex_lock: Assertion `mutex-__data.__owner == 0' failed.

Status in DBus C++:
  In Progress
Status in “dbus-cpp” package in Ubuntu:
  In Progress
Status in “indicator-network” package in Ubuntu:
  In Progress
Status in “location-service” package in Ubuntu:
  In Progress
Status in “dbus-cpp” package in Ubuntu RTM:
  In Progress
Status in “indicator-network” package in Ubuntu RTM:
  In Progress

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding indicator-network.  This problem was most recently seen with
  version 0.5.1+14.10.20141015-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/ecc14b5d54f3e0a0f1720cad0c623f81c8a16988
  contains more details.

  steps to reproduce: (need to trigger race condition)
  1. pull down network indicator
  2. toggle flight mode on and off quickly a few times
  3. click sim card 1 and 2
  4. toggle flight mode
  5. swipe up close indicators
  6. repeat steps 1-5 until crash occurs

  expected results:
  no crash happens

  actual results:
  Bluetooth indicator blinks (appear and disappear) in indicator bar at top of 
screen, and network indicator crashes. 

  additional info:
  eventually the bluetooth indicator appears stable in the indicators at the 
top of the screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1382595] Re: [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:indicator-network-service: pthread_mutex_lock.c:80: __pthread_mutex_lock: Ass

[Thomas Voß]

To clarify: The message router likely resolves to an already dead
object, and the access to the associated mutex is undefined behavior as
the member has been freed when the respective object died away before.
I'm proposing a change to dbus-cpp to robustify handling of such
situations. However, downstream projects should make sure that they
clean up correctly dynamically created objects.

** Branch linked: lp:~thomas-voss/dbus-cpp/robustify-against-dead-
objects-hanging-around

** Changed in: location-service (Ubuntu)
   Status: Invalid = Confirmed

** Changed in: location-service (Ubuntu)
 Assignee: (unassigned) = Thomas Voß (thomas-voss)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1382595

Title:
  [TOPBLOCKER] /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-
  network-service:indicator-network-service: pthread_mutex_lock.c:80:
  __pthread_mutex_lock: Assertion `mutex-__data.__owner == 0' failed.

Status in DBus C++:
  Confirmed
Status in “dbus-cpp” package in Ubuntu:
  Confirmed
Status in “indicator-network” package in Ubuntu:
  Invalid
Status in “location-service” package in Ubuntu:
  Confirmed
Status in “dbus-cpp” package in Ubuntu RTM:
  Confirmed

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding indicator-network.  This problem was most recently seen with
  version 0.5.1+14.10.20141015-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/ecc14b5d54f3e0a0f1720cad0c623f81c8a16988
  contains more details.

  steps to reproduce: (need to trigger race condition)
  1. pull down network indicator
  2. toggle flight mode on and off quickly a few times
  3. click sim card 1 and 2
  4. toggle flight mode
  5. swipe up close indicators
  6. repeat steps 1-5 until crash occurs

  expected results:
  no crash happens

  actual results:
  Bluetooth indicator blinks (appear and disappear) in indicator bar at top of 
screen, and network indicator crashes. 

  additional info:
  eventually the bluetooth indicator appears stable in the indicators at the 
top of the screen.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-cpp/+bug/1382595/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1380736] Re: Unlocking sim causes unity8 crash

[Thomas Voß]

** Branch linked: lp:~thomas-voss/qtubuntu-media/fix-races-for-access-
to-destroyed-controls

** Changed in: qtubuntu-media (Ubuntu)
   Status: New = In Progress

** Changed in: qtubuntu-media (Ubuntu)
   Importance: Undecided = Critical

** Changed in: qtubuntu-media (Ubuntu)
 Assignee: (unassigned) = Thomas Voß (thomas-voss)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1380736

Title:
  Unlocking sim causes unity8 crash

Status in Network Menu:
  Invalid
Status in “dbus-cpp” package in Ubuntu:
  New
Status in “media-hub” package in Ubuntu:
  New
Status in “qtubuntu-media” package in Ubuntu:
  In Progress
Status in “unity8” package in Ubuntu:
  New

Bug description:
  STEPS:
  1. Install a new image (Apparently it works with just re-running the wizard)
  2. While the dash is empty drag down the network indicator
  3. Click on the first unlock sim button
  4. Type in the unlock code and hit the tick
  5. System locks up

  EXPECTED:
  I expect the lock you unlock the sim and change back to the indicator

  ACTUAL:
  The system hard locks nothing works.  In the end you are forced to hard 
shutdown the phone by pressing and holding the power button till the phone 
powers down.

  Booting the Phone back up after this and everthing works as expected.
  Also waiting on the dash to fully load and fill with apps and then unlocking 
works.

To manage notifications about this bug go to:
https://bugs.launchpad.net/indicator-network/+bug/1380736/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1368519] Re: /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1

[Thomas Voß]

** Changed in: dbus-cpp (Ubuntu)
   Status: Confirmed = Invalid

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1368519

Title:
  /usr/lib/arm-linux-gnueabihf/indicator-network/indicator-network-
  
service:6:__gnu_cxx::__verbose_terminate_handler:__cxxabiv1::__terminate:std::terminate:__cxxabiv1::__cxa_throw:std::__throw_system_error

Status in “dbus-cpp” package in Ubuntu:
  Invalid
Status in “indicator-network” package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding indicator-network.  This problem was most recently seen with
  version 0.5.1+14.10.20140904-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/e2976077aa05c26721c6567aef8790b0cf5ec1ac
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1368519/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1367836] Re: Top Crasher: ubuntu-location-serviced crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

[Thomas Voß]

** Changed in: location-service (Ubuntu)
   Status: Confirmed = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1367836

Title:
  Top Crasher: ubuntu-location-serviced crashed with SIGABRT in
  __gnu_cxx::__verbose_terminate_handler()

Status in “dbus-cpp” package in Ubuntu:
  Fix Released
Status in “location-service” package in Ubuntu:
  Fix Released

Bug description:
  Hi,

  while testing location-service in utopic-proposed on mako, I've reproduced 
the exact same setup as in bug #1367835, but disabled the GPS provider to avoid 
the error described in this bug:
  1) change:
  export HERE_IMEI_FRAGMENT=$Serial
  to:
  export HERE_IMEI_FRAGMENT=35513605
  in /etc/init/ubuntu-location-provider-here-posclientd.conf to help the 
service come up on boot (see bug #1367244), not sure it helps though.

  2) change
  exec /usr/bin/ubuntu-location-serviced --bus system --provider $provider 
$poptions
  to:
  exec /usr/bin/ubuntu-location-serviced --bus system --provider 
remote::Provider --remote::Provider::name=com.ubuntu.espoo.Service.Provider 
--remote::Provider::path=/com/ubuntu/espoo/Service/Provider
  in /etc/init/ubuntu-location-service.override.

  I also manually started the trust store with start ubuntu-location-
  service-trust-stored.

  While accessing location from OSMTouch app, I've got this crash.

  Cheers,

  ProblemType: Crash
  DistroRelease: Ubuntu 14.10
  Package: ubuntu-location-service-bin 2.1+14.10.20140829-0ubuntu1
  Uname: Linux 3.4.0-5-mako armv7l
  ApportVersion: 2.14.7-0ubuntu2
  Architecture: armhf
  Date: Wed Sep 10 16:44:16 2014
  ExecutablePath: /usr/bin/ubuntu-location-serviced
  ExecutableTimestamp: 1409311427
  InstallationDate: Installed on 2014-09-10 (0 days ago)
  InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf 
(20140910-020205)
  ProcCmdline: /usr/bin/ubuntu-location-serviced --bus system --provider 
remote::Provider --remote::Provider::name=com.ubuntu.espoo.Service.Provider 
--remote::Provider::path=/com/ubuntu/espoo/Service/Provider
  ProcCwd: /
  ProcEnviron:
   TERM=linux
   PATH=(custom, no user)
  Signal: 6
  SourcePackage: location-service
  StacktraceTop:
   ?? () from /lib/arm-linux-gnueabihf/libc.so.6
   raise () from /lib/arm-linux-gnueabihf/libc.so.6
   abort () from /lib/arm-linux-gnueabihf/libc.so.6
   __gnu_cxx::__verbose_terminate_handler() () from 
/usr/lib/arm-linux-gnueabihf/libstdc++.so.6
   ?? () from /usr/lib/arm-linux-gnueabihf/libstdc++.so.6
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups:

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1367836/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1354068] Re: /usr/bin/unity8:11:std::function:SlotWrapper:core::Signal:core::dbus::Signal:operator

[Thomas Voß]

** Changed in: dbus-cpp (Ubuntu)
   Status: New = Fix Committed

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1354068

Title:
  
/usr/bin/unity8:11:std::function:SlotWrapper:core::Signal:core::dbus::Signal:operator

Status in Mir:
  Invalid
Status in “dbus-cpp” package in Ubuntu:
  Fix Committed
Status in “media-player” package in Ubuntu:
  Invalid
Status in “unity8” package in Ubuntu:
  Invalid

Bug description:
  The Ubuntu Error Tracker has been receiving reports about a problem
  regarding unity8.  This problem was most recently seen with version
  8.00+14.10.20140805-0ubuntu1, the problem page at
  https://errors.ubuntu.com/problem/8c88c781c702b88274b020e223d66d63e2d34a33
  contains more details.

To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1354068/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1358918] Re: ubuntu-location-serviced cpu usage spikes to 100% occasionally

[Thomas Voß]

** Also affects: dbus-cpp (Ubuntu)
   Importance: Undecided
   Status: New

** Changed in: dbus-cpp (Ubuntu)
   Status: New = Confirmed

** Changed in: dbus-cpp (Ubuntu)
 Assignee: (unassigned) = Thomas Voß (thomas-voss)

** Changed in: dbus-cpp (Ubuntu)
   Importance: Undecided = High

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1358918

Title:
  ubuntu-location-serviced cpu usage spikes to 100% occasionally

Status in “dbus-cpp” package in Ubuntu:
  Confirmed
Status in “location-service” package in Ubuntu:
  Confirmed

Bug description:
  Occasionally, users report the location service daemon CPU usage to
  spike and occupy an entire core of the system. Up until now, we have
  no way of reliably reproducing the issue. If you encounter it, please
  do the following:

* Report the output of /system/bin/logcat on this bug
* If possible, attach to the location service daemon process with:
   * sudo gdb -p ${PID_OF_LOCATION_SERVICE_DAEMON}
   * Call generate-core-file inside gdb
   * Attach the resuling core.${PID_OF_LOCATION_SERVICE_DAEMON} to this 
bug report

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1358918/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1329211] Re: core::dbus::Service constructor ignores return value of dbus_request_name(), hiding failures

[Thomas Voß]

** Changed in: dbus-cpp
   Status: In Progress = Fix Released

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1329211

Title:
  core::dbus::Service constructor ignores return value of
  dbus_request_name(), hiding failures

Status in DBus C++:
  Fix Released
Status in “dbus-cpp” package in Ubuntu:
  Fix Released

Bug description:
  The core::dbus::Service constructor ignores the return value of
  dbus_bus_request_name().  This means that a service might start but
  never be able to handle any method calls because its well known name
  is owned by someone else.

  When used with the core::dbus::Skeleton type, the name request flags
  are do_not_queue and replace_existing.  Looking at the libdbus API
  docs here:

  
http://dbus.freedesktop.org/doc/api/html/group__DBusBus.html#ga8a9024c78c4ea89b6271f19dbc7861b2

  The function could return one of:

   * DBUS_REQUEST_NAME_REPLY_PRIMARY_OWNER
   * DBUS_REQUEST_NAME_REPLY_EXISTS
   * DBUS_REQUEST_NAME_REPLY_ALREADY_OWNER

  The exists response should probably be treated as an error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-cpp/+bug/1329211/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1326200] Re: core::dbus::Fixture leaves stale dbus-daemon processes around if test suite terminates

[Thomas Voß]

** Changed in: dbus-cpp
   Status: In Progress = Fix Released

** Changed in: dbus-cpp (Ubuntu)
 Assignee: (unassigned) = Thomas Voß (thomas-voss)

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1326200

Title:
  core::dbus::Fixture leaves stale dbus-daemon processes around if test
  suite terminates

Status in DBus C++:
  Fix Released
Status in “dbus-cpp” package in Ubuntu:
  Fix Released

Bug description:
  If a test suite terminates without core::dbus::Fixture's destructor
  running, two stale dbus-daemon subprocesses are left running.  Among
  other things, this can lead to apparent test suite hangs when running
  under cmake/ctest: ctest doesn't consider a test to have completed
  until stdout/stderr are closed, and the dbus-daemon subprocesses hold
  those file descriptors open.  The default timeout for tests seems to
  be 2 hours, so this can introduce a long delay.

  It is clear that cases where this happens are errors, but as this
  class is intended to be used in test suites, it would be nice if it
  was a bit more robust about making sure the subprocesses are cleaned
  up.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-cpp/+bug/1326200/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1329211] Re: core::dbus::Service constructor ignores return value of dbus_request_name(), hiding failures

[Thomas Voß]

** Changed in: dbus-cpp (Ubuntu)
 Assignee: (unassigned) = Thomas Voß (thomas-voss)

** Changed in: dbus-cpp (Ubuntu)
   Status: New = In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1329211

Title:
  core::dbus::Service constructor ignores return value of
  dbus_request_name(), hiding failures

Status in DBus C++:
  In Progress
Status in “dbus-cpp” package in Ubuntu:
  In Progress

Bug description:
  The core::dbus::Service constructor ignores the return value of
  dbus_bus_request_name().  This means that a service might start but
  never be able to handle any method calls because its well known name
  is owned by someone else.

  When used with the core::dbus::Skeleton type, the name request flags
  are do_not_queue and replace_existing.  Looking at the libdbus API
  docs here:

  
http://dbus.freedesktop.org/doc/api/html/group__DBusBus.html#ga8a9024c78c4ea89b6271f19dbc7861b2

  The function could return one of:

   * DBUS_REQUEST_NAME_REPLY_PRIMARY_OWNER
   * DBUS_REQUEST_NAME_REPLY_EXISTS
   * DBUS_REQUEST_NAME_REPLY_ALREADY_OWNER

  The exists response should probably be treated as an error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/dbus-cpp/+bug/1329211/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp

[Desktop-packages] [Bug 1329089] Re: g++-4.9 binary incompatibilties with libraries built with g++-4.8

[Thomas Voß]

unorderd_map is not exposed in the API/ABI of the library

** Branch linked: lp:~thomas-voss/dbus-cpp/bump-so-name-and-major-
version

** Changed in: dbus-cpp (Ubuntu)
 Assignee: (unassigned) = Thomas Voß (thomas-voss)

** Changed in: process-cpp (Ubuntu)
   Status: New = Invalid

** Changed in: dbus-cpp (Ubuntu)
   Status: Confirmed = In Progress

-- 
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to dbus-cpp in Ubuntu.
Matching subscriptions: dp-unity
https://bugs.launchpad.net/bugs/1329089

Title:
  g++-4.9 binary incompatibilties with libraries built with g++-4.8

Status in “dbus-cpp” package in Ubuntu:
  In Progress
Status in “firefox” package in Ubuntu:
  New
Status in “gcc-4.9” package in Ubuntu:
  Confirmed
Status in “gcc-defaults” package in Ubuntu:
  Fix Released
Status in “location-service” package in Ubuntu:
  Invalid
Status in “mir” package in Ubuntu:
  New
Status in “process-cpp” package in Ubuntu:
  Invalid
Status in “qtbase-opensource-src” package in Ubuntu:
  New
Status in “unity” package in Ubuntu:
  New

Bug description:
  The location-service 0.0.3+14.10.20140512-0ubuntu1 package in utopic,
  when rebuilt against libdbus-cpp3 3.0.0+14.10.20140604-0ubuntu1 (built
  with gcc-4.8) and with current gcc-defaults (which makes g++-4.9 the
  default), fails the package build in its test suite.

   2/14 Test  #2: acceptance_tests ..***Failed   30.54 sec
  DBus daemon: 
unix:abstract=/tmp/dbus-HdW1T5UHNB,guid=188551aa5d797b663dade1425398d71b
  task-0: Started with PID: 13031
  task-0: [==] Running 2 tests from 1 test case.
  task-0: [--] Global test environment set-up.
  task-0: [--] 2 tests from LocationServiceStandalone
  task-0: [ RUN  ] LocationServiceStandalone.SessionsReceiveUpdatesViaDBus

  ** (dbus-test-runner:13025): WARNING **: Timing out at maximum wait of
  30 seconds.

  (dbus-test-runner:13025): libdbustest-CRITICAL **: dbus_test_service_run: 
assertion 'all_tasks(service, all_tasks_finished_helper)' failed
  task-0: Shutting down
  DBus daemon: Shutdown

  This test suite does *not* fail if either dbus-cpp is rebuilt with
  g++-4.9, or if location-service is built with g++-4.8.

  This implies a binary compatibility problem for C++ libraries in g++
  4.9, which is critical to resolve.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dbus-cpp/+bug/1329089/+subscriptions

-- 
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help   : https://help.launchpad.net/ListHelp