Control: retitle -1 libxaw: Uploading upstream version 1.0.16 will cause FTBFS
On 28.07.24 Thomas Dickey (dic...@his.com) wrote:
> On Sat, Jul 27, 2024 at 11:31:33PM +0200, Hilmar Preusse wrote:
> > Source: libxaw
> > Version: 2:1.0.14-1
>
> 1.0.16 is the latest version. Re
retitle -1 libxaw: Uploading upstream version 1.0.16 will cause FTBFS
On 28.07.24 Thomas Dickey (dic...@his.com) wrote:
> On Sat, Jul 27, 2024 at 11:31:33PM +0200, Hilmar Preusse wrote:
> > Source: libxaw
> > Version: 2:1.0.14-1
>
> 1.0.16 is the latest version. Retit
Source: libxaw
Version: 2:1.0.14-1
Severity: minor
Tags: upstream
Dear Maintainer,
this is rather an information than a real bug report. The latest version
of libxaw introduces a change which will break the build for at least
one package (texlive-bin).
commit d0fcbd9722ad691ca0b5873c98e8e9c236fa
On 14.02.14 Sven Joachim (svenj...@gmx.de) wrote:
Hi,
> > I guess debug of the nouveau code is relevant. Here is the bt of
> > the same core dump after installing xserver-xorg-video-nouveau-dbg.
> >
> > Further I think that bug is important -> raising sev.
>
> This might be https://bugs.freedesk
On 19.02.14 Sven Joachim (svenj...@gmx.de) wrote:
Hi,
> They will likely complain about your old kernel and mesa versions, but
> you can try (I don't think those matter in this case). Please see
> http://nouveau.freedesktop.org/wiki/Bugs/ for instructions.
>
https://bugs.freedesktop.org/show_bu
Dear Deekoo, dear Thiemo,
I believe I see the same problem. I can crash the X-Server displaying
an image larger than the screen using "display" (from imagemagick).
display doesn't scale down the image before displaying it, but
displays it in original size.
Of course I can reproduce the problem us
On 19.02.14 Sven Joachim (svenj...@gmx.de) wrote:
Hi,
> They will likely complain about your old kernel and mesa versions, but
> you can try (I don't think those matter in this case).
>
The nouveau driver is not linked w/ mesa and a userspace program. Both
should not matter.
> Please see http:/
On 15.02.14 Sven Joachim (svenj...@gmx.de) wrote:
> Am 15.02.2014 um 16:01 schrieb Hilmar Preusse:
> > On 15.02.14 Sven Joachim (svenj...@gmx.de) wrote:
> >> Am 14.02.2014 um 23:00 schrieb Hilmar Preusse:
Hi,
> >> > I guess I rather look at https://bugs.debian.org/6
On 16.02.14 Sven Joachim (svenj...@gmx.de) wrote:
> Am 15.02.2014 um 22:53 schrieb Hilmar Preusse:
Hi,
> > The only one I found was the following from upstream changelog:
> >
> > commit 2fa3397e348161a3394e2b456f065921272a056a
> > Author: Ilia Mirkin
> > Date
On 15.02.14 Sven Joachim (svenj...@gmx.de) wrote:
> Am 15.02.2014 um 16:01 schrieb Hilmar Preusse:
Hi,
> > He says, it is fixed latest in 1:1.0.10-1 (Debian testing).
>
> Yes. What I mean is that I cannot find anything in the commit logs of
> xserver-xorg-nouveau which would
On 15.02.14 Sven Joachim (svenj...@gmx.de) wrote:
> Am 14.02.2014 um 23:00 schrieb Hilmar Preusse:
Hi,
> > I guess I rather look at https://bugs.debian.org/688082 . Is this a
> > patch for it?
>
> I don't think so, but then again I don't really understand why tha
On 14.02.14 Sven Joachim (svenj...@gmx.de) wrote:
> Am 14.02.2014 um 19:42 schrieb Hilmar Preusse:
Hi,
> > I guess debug of the nouveau code is relevant. Here is the bt of
> > the same core dump after installing xserver-xorg-video-nouveau-dbg.
> >
> > Further I
severity 712545 important
stop
On 14.02.14 Hilmar Preusse (hill...@web.de) wrote:
Hi,
> I *think* I see the same problem, at least I have about the same
> backtrace. I see the problem when displaying pictures e.g. using
> display. Attached is the gdb backtrace. I you need m
Package: x11-utils
Version: 7.6+1
Severity: minor
Hi,
I just noticed that x11-utils depends on cpp. I was wondering and
consulted the changelog for an explanation. I found the following entry:
xbase-clients (1:7.2.ds2-2) unstable; urgency=low
[ Brice Goglin ]
* Restore Depends: on cpp (
On 30.11.10 Cyril Brulebois (k...@debian.org) wrote:
> Hilmar Preusse (28/11/2010):
Hi,
> > The maintainer of xdvi argued that this behavior would be correct:
> > obviously, multiple specifications for the same resource name will
> > cause a clash. Doing a similar thing wi
Dear X maintainers,
Years ago we got a bug report that multiple specifications of the
same resources is not possible for xdvi:
I invoke the actual binary, just in case the wrapper is screwing up
the arguments:
/usr/bin/xdvi.bin -xrm 'XDvi.mainTranslations: #override \
"x":quit()' -xrm 'XDvi.m
16 matches
Mail list logo