Package: x11-apps
Version: 7.7+9
Severity: normal
Tags: upstream
Hi,
Using
xwd -out steam.xwd
and clicking on any window opened by Steam gives
X Error of failed request: BadColor (invalid Colormap parameter)
Major opcode of failed request: 91 (X_QueryColors)
Resource id in failed
Hi,
the missing example code is attached here.
Simon
vkload-b0rked.tar.gz
Description: application/gzip
Package: libxext6
Version: 2:1.3.3-1.1
Severity: minor
Tags: upstream
X-Debbugs-Cc: s...@debian.org
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
I have a very basic Vulkan app that uses libXext only indirectly through
the Vulkan X11 extension, so my program is not linked against libXext
Hi,
On Wed, Oct 23, 2019 at 09:45:11AM +1300, Olly Betts wrote:
> > This is a major showstopper for linking KiCad 5 against GTK3, so this
> > requires us to keep GTK2 around longer.
> The debian kicad package has now using the GTK3 flavour of wxwidgets3.0
> for many months, so has this bug been
Package: kicad,libwxgtk3.0-gtk3-0v5,libcairo2,libpixman-1-0
Severity: important
Hi,
this bug is difficult to pin down to a specific package.
KiCad uses the graphics context from wxWidgets for rendering in the
schematic editor (which somewhat works) and the PCB editor (which fails
utterly).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
On 15.04.2015 15:59, Alex Deucher wrote:
When you say sleep, do you mean suspend/resume or dpms? Depending
on the hw involved, this patch might help:
Package: linux-image-3.16.0-4-amd64,xserver-xorg-video-radeon
Severity: normal
Hi,
I've recently installed an Acer Aspire One 725 with Debian jessie, and
found that after resuming from sleep, the display remains black (but
backlight is on) with X. Text mode consoles work fine with and without
Package: xterm
Version: 278-4
Severity: minor
Hi,
in addition to #721353, which I believe is a problem in the input method
itself, the current cursor position is not updated by xterm when a new font
is selected (see attached image).
Moving the cursor once corrects the problem, so minor -- it is
Hi,
On 03.07.2013 12:01, Zhigang Gong wrote:
The gbm device doesn't init lookup_image method and the user data. The
lookup_image is only
initialized when use the gbm device to create an egl display and then
initialize the egl drm
platform which is not our use model.
My plan for Beignet
Hi,
On 26.06.2013 10:38, Julien Cristau wrote:
the beignet package builds against libegl1-mesa, and uses the symbol
image_lookup_extension, which according to the symbols file exists since
version 8.1.
Actually that seems like a bug in beignet. image_lookup_extension is
not a public
Package: libegl1-mesa
Version: 9.1.3-6
Severity: normal
Hi,
the beignet package builds against libegl1-mesa, and uses the symbol
image_lookup_extension, which according to the symbols file exists since
version 8.1.
The dependency generated by dpkg-shlibdeps is
libegl1-mesa (= 8.1~0) |
Hi,
On Wed, Jan 20, 2010 at 04:10:14AM -0500, Thomas Dickey wrote:
I've not seen this (nor do ongoing fixes seem to be addressing it).
Can you still reproduce it?
I haven't noticed that happening it in a long time now. The box in
question exhibits other strange problems with X now, so I am
Package: xterm
Version: 250-1
Severity: normal
Hi,
since a few weeks, the selection remains highlighted in xterm on several
occasions, even if I have subsequently marked another piece of text. I
have not yet been able to identify a clear pattern when this happens. If
the application redraws the
Package: xterm
Version: 244-1
Severity: important
Starting with today's upgrade, running xterm under ratpoison and changing
the font makes the window unuseable. I suspect that xterm and ratpoison
disagree on the new window size (xterm tries to resize so that the number
of rows and columns is met,
Hi,
Drew Parsons wrote:
This has the potential to impact on any third party packages which use
libxaw6. We don't believe this should annul the package's removal
however, because
a) these packages should be rebuilt against libxaw7 anyway, and
The problem with third-party packages is that
Hi,
Thomas Dickey wrote:
it appears as if that old bug has reappeared. When the windowmanager
gives back a different ConfigureNotify than what was initially
requested, the shell process needs to be sent a SIGWINCH.
That put a different thought in my head than the similar ion3 report.
But
Package: xterm
Version: 208-1
Severity: normal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
it appears as if that old bug has reappeared. When the windowmanager
gives back a different ConfigureNotify than what was initially
requested, the shell process needs to be sent a SIGWINCH.
Thomas,
On Fri, Nov 01, 2002 at 02:46:29PM +, J.D. Hood wrote:
The question was: Why does X need APM support in order
to recover from a suspend-and-resume cycle?
Yes, and the short answer to this is that this is actually pointless. X
already receives VT_ACTIVATE and VT_DEACTIVATE events,
Thomas,
On Fri, Nov 01, 2002 at 02:46:29PM +, J.D. Hood wrote:
The question was: Why does X need APM support in order
to recover from a suspend-and-resume cycle?
Yes, and the short answer to this is that this is actually pointless. X
already receives VT_ACTIVATE and VT_DEACTIVATE events,
Thomas/others,
However, it sounds to me as if the problem isn't one that
can be fixed by X. Without APM support, X doesn't know when
a suspend-and-resume cycle occurs, and so doesn't know when it
should reinitialize hardware registers.
I thought X should reinitialize if its console is
Thomas/others,
However, it sounds to me as if the problem isn't one that
can be fixed by X. Without APM support, X doesn't know when
a suspend-and-resume cycle occurs, and so doesn't know when it
should reinitialize hardware registers.
I thought X should reinitialize if its console is
Hi,
I know this has been reported before ([1], [2], [3]), but is there any
progress on that issue (I just got my shiny new graphics card...)?
Simon
[1] http://lists.debian.org/debian-x-0101/msg00083.html
[2] http://lists.debian.org/debian-x-0106/msg00072.html
[3]
22 matches
Mail list logo