dx-packages team mailing list archive

[Adam Conrad <adconrad@xxxxxxx>]

Hello denissius, or anyone else affected,

Accepted indicator-application into saucy-proposed. The package will
build now and be available at http://launchpad.net/ubuntu/+source
/indicator-application/12.10.1+13.10.20131107-0ubuntu1 in a few hours,
and then in the -proposed repository.

Please help us by testing this new package.  See
https://wiki.ubuntu.com/Testing/EnableProposed for documentation how to
enable and use -proposed.  Your feedback will aid us getting this update
out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug,
mentioning the version of the package you tested, and change the tag
from verification-needed to verification-done. If it does not fix the
bug for you, please add a comment stating that, and change the tag to
verification-failed.  In either case, details of your testing will help
us make a better decision.

Further information regarding the verification process can be found at
https://wiki.ubuntu.com/QATeam/PerformingSRUVerification .  Thank you in
advance!

** Changed in: indicator-application (Ubuntu Saucy)
       Status: Triaged => Fix Committed

** Tags added: verification-needed

-- 
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-application in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1197788

Title:
  indicator-application-service crashed with signal 5 in
  g_type_create_instance()

Status in Application Indicators:
  Fix Committed
Status in “indicator-application” package in Ubuntu:
  Fix Committed
Status in “indicator-application” source package in Saucy:
  Fix Committed

Bug description:
  [Impact]
  Any users who starts indicator-application with an inaccessible dbus session bus.

  [Test case]
  Try to start indicator-application-service as a different user than the user currently connected (i.e. sudo -u toto /usr/lib/*/indicator-application-service )
  Observe that it does not crash and rather stops gracefully.

  [Regression potential]
  The service could fail to successfully start even when the bus should be available, in which case it should normally get respawned automatically.

  ---

  indicator-application-service crashed with signal 5 in
  g_type_create_instance()

  ProblemType: Crash
  DistroRelease: Ubuntu 13.10
  Package: indicator-application 12.10.1daily13.01.25-0ubuntu1
  ProcVersionSignature: Ubuntu 3.8.0-25.17-lowlatency 3.8.13
  Uname: Linux 3.8.0-25-lowlatency i686
  ApportVersion: 2.10.2-0ubuntu3
  Architecture: i386
  Date: Thu Jul  4 16:16:42 2013
  ExecutablePath: /usr/lib/i386-linux-gnu/indicator-application-service
  MarkForUpload: True
  ProcCmdline: /usr/lib/i386-linux-gnu/indicator-application-service
  Signal: 5
  SourcePackage: indicator-application
  StacktraceTop:
   ?? ()
   g_type_create_instance () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_newv () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
   g_object_new () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
  Title: indicator-application-service crashed with signal 5 in g_type_create_instance()
  UpgradeStatus: No upgrade log present (probably fresh install)
  UserGroups: adm admin audio cdrom dialout dip floppy lpadmin plugdev scanner video

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