Package: libglib2.0-0
Version: 2.46.0-2
Severity: critical
Tags: patch
Justification: breaks unrelated software
Dear Maintainer,
* What led up to the situation?
I upgraded package libglib2.0-0 from version 2.44.1-1.1 to version 2.46.0-2.
* What exactly did you do (or not do) that was effective (or
ineffective)?
I run the following command:
$ python -c "import gi.repository"
* What was the outcome of this action?
The process received a SIGSEGV. By trying the following command:
$ strace python -c "import gi.repository"
I saw that libgobject-2.0.so is not found (see attached log).
* What outcome did you expect instead?
No segmentation fault should occur.
As far as I know, this bug affects two packages: meld and reportbug (gtk2
interface).
I solved by creating a symbolic link to libgobject-2.0.so.0:
# ln -s /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
/usr/lib/x86_64-linux-gnu/libgobject-2.0.so
so I'm proposing to include a symbolic link to libgobject-2.0.so.0 in package
libglib2.0-0.
Moreover, after creating the symbolic link, the gtk2 interface of reportbug
shows the window, but still receives a SIGSEGV signal as soon as the mouse
pointer enters the window; however strace is not useful in this case, so I
don't know if the bug is the same as this one.
-- System Information:
Debian Release: stretch/sid
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'),
(500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.2.0-1-amd64 (SMP w/8 CPU cores)
Locale: LANG=it_IT.UTF-8, LC_CTYPE=it_IT.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
