[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#754392: marked as done (weston: segfault on exit when cms-colord.so is loaded)

Your message dated Thu, 2 Jun 2016 13:09:18 +0200
with message-id <20160602110918.GA3833@polynomio.collabora.co.uk>
and subject line Re: Bug#754392: weston: segfault on exit when cms-colord.so is loaded
has caused the Debian Bug report #754392,
regarding weston: segfault on exit when cms-colord.so is loaded
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
754392: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=754392
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: libc6
Version: 2.19-5
Severity: serious

Hi,

On my amd64 machine, weston is crashing on exit with an illegal
instruction when the colord plugin is loaded.

Using gdb shows me the following backtrace:

#0  0x00007ffff681d18b in _xbegin () at ../nptl/sysdeps/unix/sysv/linux/x86/hle.h:53
#1  __lll_lock_elision (futex=0x727ab0, adapt_count=0x727ac6, private=128) at ../nptl/sysdeps/unix/sysv/linux/x86/elision-lock.c:56
#2  0x00007fffeca9d991 in g_mutex_lock (mutex=<optimized out>) at /tmp/buildd/glib2.0-2.40.0/./glib/gthread-posix.c:209
#3  0x00007fffed732e5f in colord_idle_cancel_for_output (cms=0x7fffe0003050, o=0x6dbca0) at src/cms-colord.c:77
#4  0x00007fffed7333bf in colord_notifier_output_destroy (listener=0x7fffe00030a8, data=0x6dbca0) at src/cms-colord.c:223
#5  0x0000000000407673 in wl_signal_emit (signal=0x6dbeb0, data=0x6dbca0) at /usr/include/wayland-server.h:260
#6  0x000000000040e9a3 in weston_output_destroy (output=0x6dbca0) at src/compositor.c:3119
#7  0x00007ffff6600b23 in x11_output_destroy (output_base=0x6dbca0) at src/compositor-x11.c:497
#8  0x00007ffff6601c72 in x11_compositor_delete_window (c=0x6400c0, window=50331653) at src/compositor-x11.c:935
#9  0x00007ffff66027a2 in x11_compositor_handle_event (fd=10, mask=1, data=0x6400c0) at src/compositor-x11.c:1273
#10 0x00007ffff7bd3c22 in wl_event_loop_dispatch (loop=0x641290, timeout=<optimized out>) at ../src/event-loop.c:419
#11 0x000000000040c164 in weston_compositor_read_input (fd=9, mask=1, data=0x6400c0) at src/compositor.c:1830
#12 0x00007ffff7bd3c22 in wl_event_loop_dispatch (loop=0x630240, timeout=timeout@entry=-1) at ../src/event-loop.c:419
#13 0x00007ffff7bd2265 in wl_display_run (display=0x6301b0) at ../src/wayland-server.c:969
#14 0x000000000041116f in main (argc=1, argv=0x7fffffffe138) at src/compositor.c:4316


This is the (illegal) instruction executed:
=> 0x7ffff681d18b <__lll_lock_elision+75>:	xbeginq 0x7ffff681d191 <__lll_lock_elision+81>

These instruction are only available on Haswell+ CPU's

Cheers,

Laurent Bigonville

-- System Information:
Debian Release: jessie/sid
  APT prefers unstable
  APT policy: (500, 'unstable'), (1, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.14-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=fr_BE.utf8, LC_CTYPE=fr_BE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages libc6:amd64 depends on:
ii  libgcc1  1:4.9.0-10

libc6:amd64 recommends no packages.

Versions of packages libc6:amd64 suggests:
ii  debconf [debconf-2.0]  1.5.53
pn  glibc-doc              <none>
ii  locales                2.19-5

-- debconf information excluded

--- End Message ---
--- Begin Message --- 
On Sat, Feb 13, 2016 at 10:30:17PM +0100, Hector Oron wrote:
> On Tue, Sep 16, 2014 at 01:10:08PM +0200, Laurent Bigonville wrote:

> Do you still experience this issue with 1.9.0 in Debian?

Upstream apparently fixed it at:
  https://lists.freedesktop.org/archives/wayland-devel/2015-July/023510.html

I am closing this report as it is apparently fixed.
Please, test and reopen if the issue persists with newer packages.

regards,
-- 
  Hector Oron

Attachment: signature.asc
Description: PGP signature


--- End Message ---
Reply to: