Silence unknown option messages

[Thomi Richards]

When Qt apps start, we often get something like this printed to stderr:

"""
unknown option -- t
unknown option -- e
unknown option -- s
unknown option -- t
unknown option -- a
unknown option -- b
unknown option -- i
unknown option -- l
unknown option -- i
unknown option -- t
unknown option -- y
unknown option -- f
unknown option -- u
unknown option -- l
unknown option -- l
unknown option -- s
unknown option -- c
unknown option -- r
unknown option -- e
unknown option -- e
unknown option -- n
"""

This makes the autopilot logs significantly longer, and much harder to read. We should silence this error, perhaps by not passing options to Qt that we've handled ourselves?

[Thomi Richards (thomir-deactivatedaccount)]

Finally got a useful stack trace. The stack at that point seems to be:

#0 0x409febb0 in write () from /lib/arm-linux-gnueabihf/libc.so.6
#1 0x411241f8 in g_wakeup_signal (wakeup=0x46f05600) at /build/buildd/glib2.0-2.38.0/./glib/gwakeup.c:238
#2 0x410f5878 in g_main_context_add_poll_unlocked (context=context@entry=0x46f03ab8, priority=priority@entry=0, fd=fd@entry=0x46f03b0c) at /build/buildd/glib2.0-2.38.0/./glib/gmain.c:4133
#3 0x410f62ae in g_main_context_new () at /build/buildd/glib2.0-2.38.0/./glib/gmain.c:617
#4 0x410f632e in g_main_context_default () at /build/buildd/glib2.0-2.38.0/./glib/gmain.c:651
#5 0x4075ec3c in QEventDispatcherGlibPrivate::QEventDispatcherGlibPrivate(_GMainContext*) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#6 0x46e387d0 in QPAEventDispatcherGlibPrivate::QPAEventDispatcherGlibPrivate(_GMainContext*) () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqubuntumirserver.so
#7 0x46e3881c in QPAEventDispatcherGlib::QPAEventDispatcherGlib(QObject*) () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqubuntumirserver.so
#8 0x46e38748 in createUnixEventDispatcher() () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqubuntumirserver.so
#9 0x46e35340 in QUbuntuBaseIntegration::QUbuntuBaseIntegration (this=0x46f01840) at integration.cc:30
#10 0x46e33e66 in QUbuntuIntegration::QUbuntuIntegration (this=0x46f01840, input_factory=0x46e51824 <(anonymous namespace)::InputAdaptorFactory::instance()::global_instance>) at integration.cc:50
#11 0x46e33aaa in QUbuntuMirIntegration::QUbuntuMirIntegration (this=0x46f01840) at integration.cc:39
#12 0x46e33536 in QUbuntuMirServerIntegrationPlugin::create (this=<optimized out>, system=..., paramList=...) at main.cc:41
#13 0x40404ba8 in QGuiApplicationPrivate::createPlatformIntegration() () from /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
#14 0x404051da in QGuiApplicationPrivate::createEventDispatcher() () from /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
#15 0x40731c86 in QCoreApplication::init() () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#16 0x40731cca in QCoreApplication::QCoreApplication(QCoreApplicationPrivate&) () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5
#17 0x4040587a in QGuiApplication::QGuiApplication(int&, char**, int) () from /usr/lib/arm-linux-gnueabihf/libQt5Gui.so.5
#18 0x423780ee in QMirServerApplication::QMirServerApplication(int&, char**, ShellServerConfiguration*) () from /usr/lib/arm-linux-gnueabihf/libunity-mir.so.1
#19 0x42378162 in createQMirServerApplication () from /usr/lib/arm-linux-gnueabihf/libunity-mir.so.1
#20 0x0000b628 in _start ()

So I think the correct solution here is to make unity8 not pass command line options it handles internally to libunity-mir. Should be a simple fix.

[Andrea Cimitan (cimi)]

still a bug now that we are running with upstart?

[Launchpad Janitor (janitor)]

[Expired for Unity 8 because there has been no activity for 60 days.]