From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <thomas@archlinux.org>
Received: from mail.saout.de ([127.0.0.1])
 by localhost (mail.saout.de [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id cT7SAXHzDr8C for <dm-crypt@saout.de>;
 Tue, 16 Aug 2011 22:51:02 +0200 (CEST)
Received: from archlinux.org (gerolde.archlinux.org [66.211.214.132])
 by mail.saout.de (Postfix) with ESMTP
 for <dm-crypt@saout.de>; Tue, 16 Aug 2011 22:51:02 +0200 (CEST)
Received: from [10.23.42.17] (port-87-193-186-180.static.qsc.de
 [87.193.186.180])
 by archlinux.org (Postfix) with ESMTPSA id BE89692041
 for <dm-crypt@saout.de>; Tue, 16 Aug 2011 16:45:39 -0400 (EDT)
Message-ID: <4E4AD6F2.8020800@archlinux.org>
Date: Tue, 16 Aug 2011 22:45:38 +0200
From: =?ISO-8859-15?Q?Thomas_B=E4chler?= <thomas@archlinux.org>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
 protocol="application/pgp-signature";
 boundary="------------enig15B9B74861D7D9A812CF789D"
Subject: [dm-crypt] The weird bug again: semid XXXXXX: semop failed for
 cookie 0xdeadbeef: incorrect semaphore state
List-Id: <dm-crypt.saout.de>
List-Unsubscribe: <http://www.saout.de/mailman/options/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=unsubscribe>
List-Archive: <http://www.saout.de/pipermail/dm-crypt>
List-Post: <mailto:dm-crypt@saout.de>
List-Help: <mailto:dm-crypt-request@saout.de?subject=help>
List-Subscribe: <http://www.saout.de/mailman/listinfo/dm-crypt>,
 <mailto:dm-crypt-request@saout.de?subject=subscribe>
To: dm-crypt <dm-crypt@saout.de>

This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enig15B9B74861D7D9A812CF789D
Content-Type: text/plain; charset=ISO-8859-15
Content-Transfer-Encoding: quoted-printable

I am getting reports of this error again:

semid 491524: semop failed for cookie 0xd4dc159: incorrect semaphore stat=
e
Failed to set a proper state for notification semaphore identified by
cookie value 223199577 (0xd4dc159) to initialize waiting for incoming
notifications.

This issue is so weird that I don't know where to start. Apparently,
this problem appears whenever chromium is running, and disappears when
you quit chromium. I'm confused about this. Very confused.

I cannot see any connection here, but it has been confirmed by several
users of different distributions (several Arch users, at least one
Slackware user).

For details, please read: https://bugs.archlinux.org/task/24614

I hope anyone can help.


--------------enig15B9B74861D7D9A812CF789D
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEAREIAAYFAk5K1vIACgkQEda5KzHP/VCd1wCdGz+DUWe6genU+Ojzn2Fvue3K
Ha0An1EwpbaaH87wfA8wPPbgYhL6gYyb
=P0J5
-----END PGP SIGNATURE-----

--------------enig15B9B74861D7D9A812CF789D--