Your message dated Fri, 22 Jun 2012 19:48:50 +0000 with message-id <[🔎] E1Si9qc-000099-HS@franck.debian.org> and subject line Bug#678528: Removed package(s) from unstable has caused the Debian Bug report #382952, regarding messages "Xlib: unexpected async reply" from allegro 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 owner@bugs.debian.org immediately.) -- 382952: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=382952 Debian Bug Tracking System Contact owner@bugs.debian.org with problems
--- Begin Message ---
- To: submit@bugs.debian.org
- Subject: Re: messages "Xlib: unexpected async reply" from allegro
- From: Emmanuel Anne <manu@absysteme.fr>
- Date: Mon, 14 Aug 2006 12:26:16 +0200
- Message-id: <20060814102616.GA17218@absysteme.fr>
- In-reply-to: <20060814071222.GA8329@absysteme.fr>
- References: <20060814071222.GA8329@absysteme.fr>
Package: liballegro4.2 Version: 2:4.2.0-5 > Allegro gives this message randomly when launching a program using its > gui features (like raine : http://www.rainemu.com/) : > Xlib: unexpected async reply > > Well apparently this message is because of Xlib calls made from > different threads. The errors happens when launching the program, even > before the X11 window appears, but it doesn't happen all the time (I'd > say maybe 1 time on 3 launches ? - rather often). > Once you get this message, the program is frozen, and you have to kill > it with Ctrl-C. > > The bug DOES NOT happen with allegro-4.2.0 vanilla from > http://alleg.sf.net/, so it's probably linked to 1 of the debian > patches (I suspect the one about geting rid of libunshareable.a, but I > didn't check it). Rectification : the problem happens also in allegro-4.2.0 vanilla, I was wrong. The easiest way to reproduce it is to run the program from gdb, then it happens almost 50% of the time when starting it, it's much more rare outside of gdb. So forget this report, it's not related to debian, it's related to allegro.
--- End Message ---
--- Begin Message ---
- To: 216839-done@bugs.debian.org,238603-done@bugs.debian.org,359306-done@bugs.debian.org,382920-done@bugs.debian.org,382952-done@bugs.debian.org,395909-done@bugs.debian.org,501744-done@bugs.debian.org,634503-done@bugs.debian.org,626049-done@bugs.debian.org,
- Cc: allegro4.2@packages.debian.org, allegro4.2@packages.qa.debian.org
- Subject: Bug#678528: Removed package(s) from unstable
- From: Debian FTP Masters <ftpmaster@ftp-master.debian.org>
- Date: Fri, 22 Jun 2012 19:48:50 +0000
- Message-id: <[🔎] E1Si9qc-000099-HS@franck.debian.org>
Version: 2:4.2.2-3+rm Dear submitter, as the package allegro4.2 has just been removed from the Debian archive unstable we hereby close the associated bug reports. We are sorry that we couldn't deal with your issue properly. For details on the removal, please see http://bugs.debian.org/678528 The version of this package that was in Debian prior to this removal can still be found using http://snapshot.debian.org/. This message was generated automatically; if you believe that there is a problem with it please contact the archive administrators by mailing ftpmaster@debian.org. Debian distribution maintenance software pp. Mark Hymers (the ftpmaster behind the curtain)
--- End Message ---