[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#382706: marked as done (libgl1-mesa-dri: rendering glitches on radeon)

Your message dated Sat, 06 Mar 2010 13:02:05 +0100
with message-id <4B92443D.7000804@ens-lyon.org>
and subject line Re: Bug#382706: libgl1-mesa-dri: rendering glitches on radeon
has caused the Debian Bug report #382706,
regarding libgl1-mesa-dri: rendering glitches on radeon
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.)


-- 
382706: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=382706
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: amaya
Version: 9.4-2
Severity: grave
Justification: renders package unusable

amaya does not start. I received the following error message:

The program 'amaya' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadMatch (invalid parameter attributes)'.
  (Details: serial 20807 error_code 8 request_code 144 minor_code 5)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)


-- System Information:
Debian Release: testing/unstable
  APT prefers unstable
  APT policy: (500, 'unstable'), (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Shell:  /bin/sh linked to /bin/bash
Kernel: Linux 2.6.15-1-k7
Locale: LANG=it_IT@euro, LC_CTYPE=it_IT@euro (charmap=ISO-8859-15)

Versions of packages amaya depends on:
ii  libc6         2.3.6-3                    GNU C Library: Shared libraries an
ii  libcomerr2    1.38+1.39-WIP-2005.12.31-1 common error description library
ii  libcurl3      7.15.2-3                   Multi-protocol file transfer libra
ii  libdb4.3      4.3.29-5                   Berkeley v4.3 Database Libraries [
ii  libfreetype6  2.1.10-1                   FreeType 2 font engine, shared lib
ii  libgcc1       1:4.0.3-1                  GCC support library
ii  libglu1-xorg  6.9.0.dfsg.1-4             Mesa OpenGL utility library [X.Org
ii  libidn11      0.5.18-2                   GNU libidn library, implementation
ii  libjpeg62     6b-12                      The Independent JPEG Group's JPEG 
ii  libkrb53      1.4.3-6                    MIT Kerberos runtime libraries
ii  libmysqlclien 5.0.18-9                   mysql database client library
ii  libpng12-0    1.2.8rel-5                 PNG library - runtime
ii  libraptor1    1.4.8-3                    Raptor RDF parser and serializer l
ii  librasqal0    0.9.11-1                   Rasqal RDF query library
ii  librdf0       1.0.2-2.1                  Redland Resource Description Frame
ii  libsqlite3-0  3.2.8-1                    SQLite 3 shared library
ii  libssl0.9.8   0.9.8a-7                   SSL shared libraries
ii  libstdc++6    4.0.3-1                    The GNU Standard C++ Library v3
ii  libwxgtk2.6-0 2.6.1.2                    wxWidgets Cross-platform C++ GUI t
ii  libxml2       2.6.23.dfsg.2-2            GNOME XML library
ii  libxslt1.1    1.1.15-4                   XSLT processing library - runtime 
ii  xlibmesa-gl [ 6.9.0.dfsg.1-4             Mesa 3D graphics library [X.Org]
ii  zlib1g        1:1.2.3-11                 compression library - runtime

amaya recommends no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Regis Boudin wrote:
> Oh sorry, I had completely forgotten about this bug. I was only showing
> up on Amaya, which has since been removed from the distribution. So I
> guess this bug can probably be closed now.
>   

Thanks for the quick reply, closing.

Brice

--- End Message ---
Reply to: