Your message dated Fri, 20 Jan 2017 22:26:17 +0000
with message-id <[email protected]>
and subject line Re: Bug#850033: libepoxy: diff for NMU version 1.3.1-1.1
has caused the Debian Bug report #850033,
regarding libepoxy0: Segmentation fault, fixed upstream
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 [email protected]
immediately.)
--
850033: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=850033
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: libepoxy0
Version: 1.3.1-1
Severity: important
Dear Maintainer,
This segmentation fault:
Thread 1 "nodejs" received signal SIGSEGV, Segmentation fault.
rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37
37 ../sysdeps/x86_64/rawmemchr.S: Aucun fichier ou dossier de ce type.
(gdb) bt
#0 rawmemchr () at ../sysdeps/x86_64/rawmemchr.S:37
#1 0x00007ffff3c2a3a2 in _IO_str_init_static_internal
(sf=sf@entry=0x7fffffff9030, ptr=ptr@entry=0x0, size=size@entry=0,
pstart=pstart@entry=0x0)
at strops.c:41
#2 0x00007ffff3c19567 in __GI___isoc99_vsscanf (string=0x0,
format=0x7fffd8116f32 "%d.%d", args=args@entry=0x7fffffff9158) at
isoc99_vsscanf.c:41
#3 0x00007ffff3c19507 in __isoc99_sscanf (s=<optimized out>,
format=format@entry=0x7fffd8116f32 "%d.%d") at isoc99_sscanf.c:31
#4 0x00007fffd80f9962 in epoxy_glx_version (dpy=0x11e4800, screen=<optimized
out>) at dispatch_glx.c:60
#5 0x00007fffe2c5d8a9 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#6 0x00007fffe2c5dc5a in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#7 0x00007fffe2c66826 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#8 0x00007fffe2c63896 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#9 0x00007fffe2c537a8 in ?? () from /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#10 0x00007fffe2c281b5 in gdk_display_manager_open_display () from
/usr/lib/x86_64-linux-gnu/libgdk-3.so.0
#11 0x00007fffe311792a in gtk_init_check () from
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#12 0x00007fffe3117959 in gtk_init () from
/usr/lib/x86_64-linux-gnu/libgtk-3.so.0
#13 0x00007ffff01a4316 in WebView::Init(v8::Local<v8::Object>,
v8::Local<v8::Object>) ()
from
/home/eda/public_nodejs/dfm2/production/node_modules/webkitgtk/lib/webkitgtk.node
#14 0x0000000000ae35b5 in node::DLOpen(v8::FunctionCallbackInfo<v8::Value>
const&) ()
#15 0x000000000067618a in v8::internal::FunctionCallbackArguments::Call(void
(*)(v8::FunctionCallbackInfo<v8::Value> const&)) ()
happens when running a webkit2gtk instance in Xvfb, on a server without any
kind of graphic capability.
I tried to upgrade the debian package to upstream libepoxy0@0aa9d1bc (because
i'm that kind of guy)
and the segmentation fault doesn't happen there.
After bisection, i found that those three patches fix the issue:
https://github.com/anholt/libepoxy/commit/b3b8bd9af7bf1fcfe544fd131f4d4f0d117ae7bc.patch
https://github.com/anholt/libepoxy/commit/8d58c890646fc1f43bcab702bb9ed6bae94daefe.patch
https://github.com/anholt/libepoxy/commit/b8d609e8f9fc1f9c4ff359adb2c1c44619a9e7cf.patch
Hopefully you will apply them to current 1.3.1 version.
Please tell me if you need me to do it.
Regards,
Jérémy
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (650, 'testing'), (600, 'unstable'), (500, 'testing-debug')
Architecture: amd64 (x86_64)
Kernel: Linux 4.8.0-2-amd64 (SMP w/12 CPU cores)
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libepoxy0 depends on:
ii libc6 2.24-8
libepoxy0 recommends no packages.
libepoxy0 suggests no packages.
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 1.3.1-1.1
On Fri, 20 Jan 2017 at 23:19:54 +0100, Jérémy Lal wrote:
> I thought i did what was necessary - the 1.3.1-2 i uploaded today has the
> changelog entry of the 1.3.1-1.1 nmu.
> Do i miss something ?
Ah, I think I see what's happened... you didn't pass -v1.3.1-1 to
dpkg-buildpackage (and the NMU never reached the archive because your
maintainer upload preempted it), so the .changes didn't mention #850033,
so the BTS didn't close the bug. Closing it now.
S
--- End Message ---
