touch-packages team mailing list archive

[Albert Astals Cid <albert.astals@xxxxxxxxxxxxx>]

So they all have the same stacktrace

#0  0xb61659a6 in ?? () from /lib/arm-linux-gnueabihf/libc.so.6
 No symbol table info available.
 #1  0xb617362e in raise () from /lib/arm-linux-gnueabihf/libc.so.6
 No symbol table info available.
 #2  0xb6174332 in abort () from /lib/arm-linux-gnueabihf/libc.so.6
 No symbol table info available.
 #3  0xb638ecdc in QMessageLogger::fatal(char const*, ...) const () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
 No symbol table info available.
 #4  0xb3ed8a34 in ?? () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqpa-ubuntumirclient.so
 No symbol table info available.
 #5  0xb3edb2a4 in ?? () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqpa-ubuntumirclient.so
 No symbol table info available.
 #6  0xb6d0e95e in QPlatformIntegrationFactory::create(QString const&, QStringList const&, int&, char**, QString const&) () from /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
 No symbol table info available.
 #7  0xb6d16878 in QGuiApplicationPrivate::createPlatformIntegration() () from /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
 No symbol table info available.
 #8  0xb6d17096 in QGuiApplicationPrivate::createEventDispatcher() () from /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
 No symbol table info available.
 #9  0xb6501540 in QCoreApplication::init() () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
 No symbol table info available.
 #10 0xb65015ca in QCoreApplication::QCoreApplication(QCoreApplicationPrivate&) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
 No symbol table info available.
 #11 0xb6d183fa in QGuiApplication::QGuiApplication(int&, char**, int) () from /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
 No symbol table info available.
 #12 0x000134f2 in ?? ()
 No symbol table info available.
 #13 0xb6165776 in __libc_start_main () from /lib/arm-linux-gnueabihf/libc.so.6
 No symbol table info available.
 #14 0x0001401c in _start ()

Which as far as i understand means that it could not find a Mir server
and is aborting.

That makes sense for the cases where unity8 had also crashed, but for ones like
http://people.canonical.com/~platform-qa/power-results/2015-07-13_02:02:39-krillin-62-power_usage_idle/1/var-crash/
where unity8 did not crash it may indeed be a real bug.

Maybe we're starting unity8-dash too early?

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

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1475526

Title:
  unity8-dash crashes during power tests

Status in qtubuntu package in Ubuntu:
  New
Status in unity8 package in Ubuntu:
  New

Bug description:
  Unity8-dash crashes fairly often while running power usage tests.  I
  hope someone will be able to determine the root cause based on crash
  dumps and other logs.

  Here are some of the 170 instances I've seen so far... inside each are
  numbered directories for each test run, and the crash dumps are inside
  of those under var-crash/ .

  Arale rc-proposed 61, runs 2, 3, and 4:
  http://people.canonical.com/~platform-qa/power-results/2015-07-16_18:21:18-arale-61-power_usage_display_on/

  Arale devel-proposed 61, runs 2, 5, and 8:
  http://people.canonical.com/~platform-qa/power-results/2015-07-16_21:58:20-arale-61-power_usage_idle/

  Arale devel-proposed 60, runs 1, 2, 6, and 7:
  http://people.canonical.com/~platform-qa/power-results/2015-07-16_15:26:03-arale-60-power_usage_flight_mode_on/

  Krillin rc-proposed 62, runs 1, 3, 4, 5, 6, 7, and 8:
  http://people.canonical.com/~platform-qa/power-results/2015-07-13_02:02:39-krillin-62-power_usage_idle/

  Krillin devel-proposed 132, runs 1, 3, 6, and 7:
  http://people.canonical.com/~platform-qa/power-results/2015-07-13_22:02:04-krillin-132-power_usage_display_on/

  These are merely samples from recent test runs. I have plenty more if
  you need them, or can add additional logging to get more data from
  future tests.

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