Xmir crashed with SIGABRT [libmirclient crashed in send_message()]

Bug #1666514 reported by dinamic
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Incomplete
Undecided
Unassigned
xorg-server (Ubuntu)
Incomplete
Undecided
Unassigned

Bug Description

Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()

ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: xmir 2:1.18.4-1ubuntu9
ProcVersionSignature: Ubuntu 4.10.0-9.11-generic 4.10.0
Uname: Linux 4.10.0-9-generic x86_64
.tmp.unity_support_test.0:

ApportVersion: 2.20.4-0ubuntu2
Architecture: amd64
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
CompositorUnredirectDriverBlacklist: '(nouveau|Intel).*Mesa 8.0'
CompositorUnredirectFSW: true
CrashCounter: 1
CurrentDesktop: Unity:Unity7
Date: Tue Feb 21 14:41:05 2017
DistUpgraded: Fresh install
DistroCodename: zesty
DistroVariant: ubuntu
ExecutablePath: /usr/bin/Xmir
ExtraDebuggingInterest: Yes, if not too technical
GraphicsCard:
 Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0102] (rev 09) (prog-if 00 [VGA controller])
   Subsystem: ASRock Incorporation 2nd Generation Core Processor Family Integrated Graphics Controller [1849:0102]
InstallationDate: Installed on 2016-12-12 (70 days ago)
InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Alpha amd64 (20161108)
MachineType: To Be Filled By O.E.M. To Be Filled By O.E.M.
ProcCmdline: Xmir -rootless -displayfd 3 -mir inkscape_inkscape_1880
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.10.0-9-generic root=UUID=61c77455-e5f4-4663-b879-b62378732cb9 ro quiet splash vt.handoff=7
Signal: 6
SourcePackage: xorg-server
StacktraceTop:
 __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
 ?? () from /usr/lib/x86_64-linux-gnu/libmirclient.so.9
Title: Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 03/03/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: P1.10
dmi.board.name: H61M-VS
dmi.board.vendor: ASRock
dmi.chassis.asset.tag: To Be Filled By O.E.M.
dmi.chassis.type: 3
dmi.chassis.vendor: To Be Filled By O.E.M.
dmi.chassis.version: To Be Filled By O.E.M.
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrP1.10:bd03/03/2011:svnToBeFilledByO.E.M.:pnToBeFilledByO.E.M.:pvrToBeFilledByO.E.M.:rvnASRock:rnH61M-VS:rvr:cvnToBeFilledByO.E.M.:ct3:cvrToBeFilledByO.E.M.:
dmi.product.name: To Be Filled By O.E.M.
dmi.product.version: To Be Filled By O.E.M.
dmi.sys.vendor: To Be Filled By O.E.M.
version.compiz: compiz 1:0.9.13.1+17.04.20170109-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.75-1
version.libgl1-mesa-dri: libgl1-mesa-dri 17.0.0-1ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 17.0.0-1ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.18.4-1ubuntu9
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:7.8.0-1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20160706-1ubuntu1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.13-1
xserver.bootTime: Tue Feb 21 14:46:04 2017
xserver.configfile: default
xserver.errors:
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
 /dev/dri/card0: failed to set DRM interface version 1.4: Permission denied
xserver.logfile: /var/log/Xorg.0.log
xserver.version: 2:1.18.4-1ubuntu9
xserver.video_driver: modeset

Revision history for this message
dinamic (dinamic6661) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __gnu_cxx::__verbose_terminate_handler() () from /tmp/apport_sandbox_GyTReL/usr/lib/x86_64-linux-gnu/libstdc++.so.6
 __cxxabiv1::__terminate(void (*)()) () from /tmp/apport_sandbox_GyTReL/usr/lib/x86_64-linux-gnu/libstdc++.so.6
 std::terminate() () from /tmp/apport_sandbox_GyTReL/usr/lib/x86_64-linux-gnu/libstdc++.so.6
 __cxa_rethrow () from /tmp/apport_sandbox_GyTReL/usr/lib/x86_64-linux-gnu/libstdc++.so.6
 send_message (fds=..., invocation=..., body=..., this=0x55e389cc68f0) at ./src/client/rpc/mir_protobuf_rpc_channel.cpp:280

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in xorg-server (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
tags: added: xmir
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

If you can reproduce the problem, please check to see if it happens as a result of the server (unity8) crashing.

summary: - Xmir crashed with SIGABRT in __gnu_cxx::__verbose_terminate_handler()
+ Xmir crashed with SIGABRT [libmirclient crashed in send_message()]
Changed in xorg-server (Ubuntu):
status: New → Incomplete
Changed in mir:
status: New → Incomplete
Changed in xorg-server (Ubuntu):
importance: Medium → Undecided
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Oh here it is from the JournalErrors.txt. It appears Gnome Screensaver failing to connect to the server (which is expected with Unity8 since it will reject regular apps) has indirectly led to Xmir crashing.

So how or why is Gnome Screensaver running?...

Feb 21 13:07:31 username-desktop org.gnome.ScreenSaver[2672]: Failed to connect to Mir: Failed to connect: not accepted by server
Feb 21 13:07:31 username-desktop org.gnome.ScreenSaver[2672]: [2017-02-21 13:07:31.883892] <ERROR> MirConnectionAPI: Caught exception at client library boundary (in mir_connection_release): /build/mir-rgB9wX/mir-0.26.1+17.04.20170209.1/src/client/rpc/stream_socket_transport.cpp(168): Throw in function virtual void mir::client::rpc::StreamSocketTransport::send_message(const std::vector<unsigned char>&, const std::vector<mir::Fd>&)
Feb 21 13:07:31 username-desktop org.gnome.ScreenSaver[2672]: Dynamic exception type: boost::exception_detail::clone_impl<boost::exception_detail::error_info_injector<mir::socket_disconnected_error> >
Feb 21 13:07:31 username-desktop org.gnome.ScreenSaver[2672]: std::exception::what: Failed to send message to server: Broken pipe
Feb 21 13:07:31 username-desktop org.gnome.ScreenSaver[2672]: [boost::errinfo_errno_*] = 32, "Broken pipe"
Feb 21 13:07:31 username-desktop org.gnome.ScreenSaver[2672]: Unable to init server: Could not connect: Connection refused
Feb 21 13:07:31 username-desktop gnome-screensav[3150]: Unable to initialize GTK+

Revision history for this message
Daniel van Vugt (vanvugt) wrote :

OK, I've generalised bug 1627311. This appears to be the same issue.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.