mir_demo_server segfaults in schroot
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Running mir_demo_server and miral-shell on a schroot produces the following segfault:
-------
error
-------
[2017-03-30 08:25:25.139004] x11-display: 1 visual(s) found
[2017-03-30 08:25:25.139028] x11-display: Using the first one :
[2017-03-30 08:25:25.139053] x11-display: ID : 32
[2017-03-30 08:25:25.139072] x11-display: screen : 0
[2017-03-30 08:25:25.139080] x11-display: depth : 24
[2017-03-30 08:25:25.139086] x11-display: red_mask : 0xFF0000
[2017-03-30 08:25:25.139093] x11-display: green_mask : 0xFF00
[2017-03-30 08:25:25.139099] x11-display: blue_mask : 0xFF
[2017-03-30 08:25:25.139105] x11-display: colormap_size : 256
[2017-03-30 08:25:25.139111] x11-display: bits_per_rgb : 8
[2017-03-30 08:25:25.159633] mirserver: Using software cursor
sh: 1: /usr/share/
ERROR: Throw location unknown (consider using BOOST_THROW_
Dynamic exception type: boost::
std::exception:
------------------
gdb output:
------------------
mir_demo_server has no bt.
miral-shell gdb output: https:/
-------
schroot desktop configuration:
-------
config:
[zesty-zapus]
description=Ubuntu zesty zapus (17.04)
type=directory
directory=
users=root,sbuild
groups=adm,eleni
profile=desktop
personality=linux
preserve-
aliases=zz
fstab:
Lack of a core file/backtrace appears to be Mir's fault: server_ example. cpp: char const command_fmt[] = "/usr/share/ apport/ recoverable_ problem --pid %d";
examples/
No application should be doing that. We have error reporting built into the OS, which is more reliable.
Try this: error-abort
$ ulimit -c unlimited
$ mir_demo_server --on-fatal-
Do you get a core file?