unity8-greeter aborts at start in libprotobuf

Bug #1655052 reported by Michael Zanetti
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
mir (Ubuntu)
Confirmed
Undecided
Unassigned
unity8 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Machine is a MacBook with intel graphics.
After installing unity8-greeter and rebooting all I get is a black screen and this core dump. I've heard this from other people too by now so it doesn't seem to be my machine only.

#0 0x00007f483d554428 in __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:54
#1 0x00007f483d55602a in __GI_abort () at abort.c:89
#2 0x00007f483d5967ea in __libc_message (do_abort=do_abort@entry=2, fmt=fmt@entry=0x7f483d6af2e0 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/posix/libc_fatal.c:175
#3 0x00007f483d59ee0a in malloc_printerr (ar_ptr=<optimized out>, ptr=<optimized out>, str=0x7f483d6ac0ca "free(): invalid size", action=3) at malloc.c:5004
#4 _int_free (av=<optimized out>, p=<optimized out>, have_lock=0) at malloc.c:3865
#5 0x00007f483d5a298c in __GI___libc_free (mem=<optimized out>) at malloc.c:2966
#6 0x00007f47faafb901 in google::protobuf::internal::DestroyDefaultRepeatedFields() () from /usr/lib/x86_64-linux-gnu/libprotobuf.so.9
#7 0x00007f483320f72b in google::protobuf::ShutdownProtobufLibrary() () from /usr/lib/x86_64-linux-gnu/libprotobuf-lite.so.9
#8 0x00007f48338df0d9 in ?? () from /usr/lib/x86_64-linux-gnu/libmirprotobuf.so.3
#9 0x00007f483fc0bc17 in _dl_fini () at dl-fini.c:235
#10 0x00007f483d558ff8 in __run_exit_handlers (status=0, listp=0x7f483d8e25f8 <__exit_funcs>, run_list_atexit=run_list_atexit@entry=true) at exit.c:82
#11 0x00007f483d559045 in __GI_exit (status=<optimized out>) at exit.c:104
#12 0x00007f483d53f837 in __libc_start_main (main=0x4077e0, argc=2, argv=0x7ffd3ee9bab8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffd3ee9baa8)
    at ../csu/libc-start.c:325
#13 0x0000000000407bd9 in _start ()

description: updated
description: updated
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in mir (Ubuntu):
status: New → Confirmed
Changed in unity8 (Ubuntu):
status: New → Confirmed
Revision history for this message
Michael Terry (mterry) wrote :

This was observed for both of us with xenial+overlay.

Revision history for this message
Michael Terry (mterry) wrote :

It's reported to work in zesty.

Revision history for this message
Gerry Boland (gerboland) wrote :

Please paste in the output of
dpkg -l | grep mir
and the contents of the greeter process log around the time of this crash.

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

The abort is from heap corruption bug 1535297. unity8-greeter must be throwing or crashing for a different reason prior to that.

So there are two bugs here. The secondary crash from heap corruption that you see is bug 1535297. But it sounds like unity8-greeter is crashing for some other reason prior to that which is the trigger. You'll need to remove/disable your default exception handling to find out what the Unity8-greeter crash is in the first place (and get a stack trace of it).

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.