@Daniel I see your point about Mir. Anyway, all I'm saying is this problem manifested via https://errors.ubuntu.com/problem/bcb050f97778eb836056c1c48139bcde30ed0bcb is completely different from the original problem described in this bug. The only common thing is qFatal() gets called. In the original problem it was called directly by unity8-dash in response to boost throwing exception on incorrect locale (which was fixed by the attached MP). In this new case this is something else in the stack calling qFatal and aborting unity8-dash and I see no evidence of locale being involved.
To sum it up, I think it's a different bug and I don't think unity- scopes-shell (the dash) or unity-scopes-api are responsible for this. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity-scopes-shell in Ubuntu. https://bugs.launchpad.net/bugs/1363946 Title: unity8-dash crashed with SIGABRT in qt_message_fatal() under incorrect locale Status in Canonical System Image: Confirmed Status in unity-scopes-api package in Ubuntu: Confirmed Status in unity-scopes-shell package in Ubuntu: Fix Released Bug description: unity8-dash gets into a respawn loop when the selected locale is unavailable. While it's understood that incorrect locale might result in unexpected behaviour, but aborting feels excessive. .log file mentions: ERROR! Caught unity::scopes::ConfigException: Cannot instantiate run time for client, config file: : unity::scopes::MiddlewareException: cannot initialize zmq middleware for scope c-17178aae00000000: locale::facet::_S_create_c_locale name not ProblemType: Crash DistroRelease: Ubuntu 14.10 Package: unity8 8.00+14.10.20140828.1-0ubuntu1 Uname: Linux 3.4.0-5-mako armv7l ApportVersion: 2.14.7-0ubuntu1 Architecture: armhf CurrentDesktop: Unity Date: Mon Sep 1 11:55:15 2014 ExecutablePath: /usr/bin/unity8-dash ExecutableTimestamp: 1409258182 InstallationDate: Installed on 2014-09-01 (0 days ago) InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140901-020204) LocalLibraries: /android/system/lib/libGLES_trace.so /android/system/lib/libstlport.so /android/system/lib/libgccdemangle.so /android/system/lib/libm.so /android/system/lib/libcorkscrew.so /android/system/lib/liblog.so /android/system/lib/libstdc++.so /android/system/lib/libutils.so /android/system/lib/libc.so /android/system/lib/libcutils.so /android/system/lib/libGLESv2.so /android/system/lib/libEGL.so /android/system/lib/libdsyscalls.so ProcCmdline: unity8-dash --desktop_file_hint=/usr/share/applications/unity8-dash.desktop ProcCwd: /home/phablet Signal: 6 SourcePackage: unity8 StacktraceTop: ?? () from /lib/arm-linux-gnueabihf/libc.so.6 raise () from /lib/arm-linux-gnueabihf/libc.so.6 abort () from /lib/arm-linux-gnueabihf/libc.so.6 QMessageLogger::fatal(char const*, ...) const () from /usr/lib/arm-linux-gnueabihf/libQt5Core.so.5 ?? () from /usr/lib/arm-linux-gnueabihf/qt5/plugins/platforms/libqpa-ubuntumirclient.so Title: unity8-dash crashed with SIGABRT in raise() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dialout dip plugdev sudo tty video To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1363946/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
