desktop-packages team mailing list archive

[marmuta <1432428@xxxxxxxxxxxxxxxxxx>]

> How can I get more debug info, or is the crash file of any help?
You should be able to  file another bug report with your crash file:
$ ubuntu-bug /var/log/_usr_lib_unity_unity-panel-service.1000.crash
If that worked you may want to duplicate this bug to the new one.

>From what I can tell the crash seems to happen in libatk-bridge-2.0, see attachment. I ran
$ sudo gdb -p $(pidof unity-panel-service) -batch -ex 'c' -ex 'bt full'
then restarted Onboard and clicked the panel once. It doesn't always happen right away, but if I keep trying it will eventually. There might be a race with accessibles appearing/disappearing at the wrong time. I'm not sure if we can influence this from Onboard's side, but I'm going to experiment a bit.


** Attachment added: "unity-panel-service-gdb-backtrace.txt"
   https://bugs.launchpad.net/ubuntu/+source/onboard/+bug/1432428/+attachment/4347147/+files/unity-panel-service-gdb-backtrace.txt

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

Title:
  unity-panel-service crashes when clicking onboard indicator

Status in onboard package in Ubuntu:
  New

Bug description:
  When clicking the onboard indicator for the first time (after starting
  onboard), it can cause  a crash of unity-panel-service. I never got
  crashes of unity-panel-service in connection with other indicators or
  applications, so I suppose it is something specific to the way how
  onboard creates its indicator.

  Apport is regularly collecting the information for this crash, but
  then it quietly disappears, without telling me whether the crash was
  automatically reported and to where. Unfortunately I don't have any
  references / bug report numbers etc. but I have a file
  _usr_lib_unity_unity-panel-service.1000.crash (13MB) that apport
  apparently created (I don't which format it is). I was hoping there is
  a chance someone here could find out more than when I report it to
  unity, because it happens very specifically when using onboard.  How
  can I get more debug info, or is the crash file of any help?

  Ubuntu 14.10 64bit
  onboard 1.1.0+1949-0ppa1~utopic
  unity 7.3.1+14.10.20141016-0ubuntu1

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