dx-packages team mailing list archive

[Launchpad Bug Tracker <1197788@xxxxxxxxxxxxxxxxxx>]

This bug was fixed in the package indicator-application -
12.10.1+14.04.20131125-0ubuntu1

---------------
indicator-application (12.10.1+14.04.20131125-0ubuntu1) trusty; urgency=low

  [ Charles Kerr ]
  * When we can't get a handle to the system bus, exit gracefully
    instead of crashing. (LP: #1197788)

  [ Ted Gould ]
  * Switch indicator application over to having an upstart job for
    managing the service. Also make it emit it's own event for when
    application indicators should be started so we can clean up the boot
    sequence. (LP: #1185565)

  [ Ubuntu daily release ]
  * Automatic snapshot from revision 242
 -- Ubuntu daily release <ps-jenkins@xxxxxxxxxxxxxxxxxxx>   Mon, 25 Nov 2013 03:55:09 +0000

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

-- 
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 Released
Status in “indicator-application” source package in Saucy:
  Fix Released

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