Your message dated Thu, 2 Oct 2014 21:27:35 +0300
with message-id <20141002182735.GG3775@sid.nuvreauspam>
and subject line Re: Bug#763787: libglib2.0-0: applications abort with "Attempt
to unlock mutex that was not locked" message
has caused the Debian Bug report #763787,
regarding libglib2.0-0: applications abort with "Attempt to unlock mutex that
was not locked" message
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 ow...@bugs.debian.org
immediately.)
--
763787: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=763787
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
On Jo, 02 oct 14, 20:20:43, Kalle Sandström wrote:
> Source: libglib2.0-0
> Version: 2.42.0-1
> Severity: grave
> Justification: renders package unusable
Due to a bug in reportbug your report is currently not assigned to any
package. Normally I'd just reassign it, but...
> 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.
... if you want to supply additional information to that bug please do
so either using reportbug or simply by sending e-mail to
<bugnumber>@bugs.debian.org. I'm closing this bug as it doesn't seem to
provide any new information.
Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic
http://nuvreauspam.ro/gpg-transition.txt
signature.asc
Description: Digital signature
--- End Message ---
