Source: libglib2.0-0
Version: 2.42.0-1
Severity: grave
Justification: renders package unusable
Dear Maintainer,
* What led up to the situation?
- customary apt-get upgrade from testing
* What exactly did you do (or not do) that was effective (or
ineffective)?
- start of application (deadbeef, sonata) from window manager or terminal
window
* What was the outcome of this action?
- window appears, then disappears instantly
- error message on terminal window
* What outcome did you expect instead?
- window appears, application enters usable state
Downgrading all glib2 packages to 2.41.1-2 from snapshot.debian.org solves the
problem, as described above, entirely.
I've classified the bug as grave and "rendering package unusable", however,
since glib2 provides no independent functionality to the flesh-and-blood user,
this implies unusability in packages that utilize glib2.
I'm surprised that this sort of garba^Wunfortunate malfunction, for which bug
#758619 has existed since 19th of August this year, can still hit testing; and
that it has seemingly gone untested to a degree at which the bug hasn't been
seen by the glib2 maintainers. Nor, seemingly, glib2's developers. Or anyone
else in the chain of consumption.
This report may be merged with #758619 since terminal-mode reportbug didn't
offer to do so already.
Regards,
-KS
-- System Information:
Debian Release: jessie/sid
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 3.16.3+ (SMP w/8 CPU cores; PREEMPT)
Locale: LANG=C, LC_CTYPE=fi_FI.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
