Bug#671747: mesa: Ship drirc
Source: mesa Version: 8.0.2-2 Severity: wishlist Hi, Upstream added a way to set some application specific options (for broken applications), and added some default values. It's stored in the drirc file. Could you please consider shipping this? Maybe in an arch all package? Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20120506155309.ga21...@roeckx.be
Bug#514395: LUT settings are not restored after switching to console.
On Fri, Jan 28, 2011 at 09:55:51AM +0100, Cyril Brulebois wrote: > Hi Kurt, > > Kurt Roeckx (12/02/2009): > > On Thu, Feb 12, 2009 at 11:31:20AM +0100, Michel Dänzer wrote: > > > AFAICT the driver RandR 1.2 code just sets the LUT values passed > > > in by the X server, so I'm reassigning. If this still happens with > > > xserver-xorg-core from experimental, you may want to report it > > > upstream. > > > > So I've just reported it upstream. > > thanks. Just checking, not fixed in 1.9.4rc1 (currently in > experimental)? It seems to be working as expected now. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110227235626.ga30...@roeckx.be
Bug#386028: xserver-xorg-video-tdfx: Characters corrupted when switching to console.
found 386028 1:1.4.3-2 thanks On Tue, Jan 18, 2011 at 12:46:37AM +0100, Cyril Brulebois wrote: > Kurt Roeckx (05/05/2007): > > This is still perfectly reproducible in etch. I've even tried without > > drm enabled now. > > What about lenny or squeeze? Still seeing it in squeeze. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20110118210945.ga8...@roeckx.be
Re: xorg-server FTBFS'd on lafayette
On Tue, Apr 06, 2010 at 03:35:51PM +0200, Cyril Brulebois wrote: > Hi folks, > > I've just noticed this: > | LINK msp3430_drv.la > | gcc: Internal error: Segmentation fault (program collect2) > | Please submit a full bug report. > | See for instructions. > | make[5]: *** [msp3430_drv.la] Error 1 > > Could you please give xorg-server back so as to make sure it's > reproducible before someone spends some time on trying to debug > what's happening here? lafayette is known to have some issues. We've enabled it building unstable again to see if they got fixed in the mean time or not. I always give such packages back when I see them, and so did this for xorg-server too. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100406162107.ga21...@roeckx.be
Bug#569430: Processed: found 569430 in 7.5+4
On Sat, Mar 20, 2010 at 12:07:15PM +0100, Brice Goglin wrote:
> Debian Bug Tracking System wrote:
> >
> >> found 569430 7.5+4
> >>
>
> Please send the corresponding log.
https://buildd.debian.org/fetch.cgi?pkg=x11-apps;ver=7.5%2B4;arch=i386;stamp=1268438345
Note that the buildd uses:
$ENV{'DEB_BUILD_OPTIONS'} = 'parallel=4';
Kurt
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100320120031.ga11...@roeckx.be
Bug#574017: xserver-xorg-core: Don't put an buildd@ address in the log file.
Package: xserver-xorg-core Hi, I've just had an other user report a problem to bui...@xxx.debian.org. This is obviously not a address to contact if you have a problem. My only guess why he contacted that address is that you have something like this in /var/log/Xorg.0.log: Build Date: 16 February 2010 10:23:38AM xorg-server 2:1.7.5-1 (bui...@brahms.debian.org) Please don't put it there in the form of email address. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/20100315181911.ga15...@roeckx.be
Bug#523415: corrupted rendering
On Mon, Jun 15, 2009 at 11:46:31PM +0200, Kurt Roeckx wrote: > On Wed, Jun 10, 2009 at 12:20:04AM +0200, Kurt Roeckx wrote: > > On Tue, Jun 09, 2009 at 11:40:35PM +0200, Kurt Roeckx wrote: > > > On Tue, Jun 09, 2009 at 07:11:37AM +0200, Brice Goglin wrote: > > > > Kurt Roeckx wrote: > > > > > On Thu, Apr 16, 2009 at 10:38:43PM +0200, Brice Goglin wrote: > > > > > > > > > >> Kurt Roeckx wrote: > > > > >> > > > > >>> That removes the line, but does not solve the problem. > > > > >>> > > > > >>> > > > > >> Right, removing write-combining is only supposed to decrease > > > > >> performance :) > > > > >> > > > > > > > > > > So I'm still seeing this problem with the latest version in > > > > > unstable (2:2.7.1-1) and kernel linux-image-2.6.29-2-686 > > > > > 2.6.29-5. > > > > > > > > > > Do you have any other idea what we can try? > > > > > > > > > > > > > Did you try a 2.6.30-rc* kernel? Some packages are available at > > > > http://kernel-archive.buildserver.net/debian-kernel/ > > > > > > linux-image-2.6.30-rc8-686 fixed my problem. > > > > There still is some corruption, but it's alot less. > > The released 2.6.30 seems to be fixing that issue too. Currently > don't see anything wrong. Of course it starts just after you send a mail. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#523415: corrupted rendering
On Wed, Jun 10, 2009 at 12:20:04AM +0200, Kurt Roeckx wrote: > On Tue, Jun 09, 2009 at 11:40:35PM +0200, Kurt Roeckx wrote: > > On Tue, Jun 09, 2009 at 07:11:37AM +0200, Brice Goglin wrote: > > > Kurt Roeckx wrote: > > > > On Thu, Apr 16, 2009 at 10:38:43PM +0200, Brice Goglin wrote: > > > > > > > >> Kurt Roeckx wrote: > > > >> > > > >>> That removes the line, but does not solve the problem. > > > >>> > > > >>> > > > >> Right, removing write-combining is only supposed to decrease > > > >> performance :) > > > >> > > > > > > > > So I'm still seeing this problem with the latest version in > > > > unstable (2:2.7.1-1) and kernel linux-image-2.6.29-2-686 > > > > 2.6.29-5. > > > > > > > > Do you have any other idea what we can try? > > > > > > > > > > Did you try a 2.6.30-rc* kernel? Some packages are available at > > > http://kernel-archive.buildserver.net/debian-kernel/ > > > > linux-image-2.6.30-rc8-686 fixed my problem. > > There still is some corruption, but it's alot less. The released 2.6.30 seems to be fixing that issue too. Currently don't see anything wrong. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#523415: corrupted rendering
On Tue, Jun 09, 2009 at 11:40:35PM +0200, Kurt Roeckx wrote: > On Tue, Jun 09, 2009 at 07:11:37AM +0200, Brice Goglin wrote: > > Kurt Roeckx wrote: > > > On Thu, Apr 16, 2009 at 10:38:43PM +0200, Brice Goglin wrote: > > > > > >> Kurt Roeckx wrote: > > >> > > >>> That removes the line, but does not solve the problem. > > >>> > > >>> > > >> Right, removing write-combining is only supposed to decrease performance > > >> :) > > >> > > > > > > So I'm still seeing this problem with the latest version in > > > unstable (2:2.7.1-1) and kernel linux-image-2.6.29-2-686 > > > 2.6.29-5. > > > > > > Do you have any other idea what we can try? > > > > > > > Did you try a 2.6.30-rc* kernel? Some packages are available at > > http://kernel-archive.buildserver.net/debian-kernel/ > > linux-image-2.6.30-rc8-686 fixed my problem. There still is some corruption, but it's alot less. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#523415: corrupted rendering
On Tue, Jun 09, 2009 at 07:11:37AM +0200, Brice Goglin wrote: > Kurt Roeckx wrote: > > On Thu, Apr 16, 2009 at 10:38:43PM +0200, Brice Goglin wrote: > > > >> Kurt Roeckx wrote: > >> > >>> That removes the line, but does not solve the problem. > >>> > >>> > >> Right, removing write-combining is only supposed to decrease performance :) > >> > > > > So I'm still seeing this problem with the latest version in > > unstable (2:2.7.1-1) and kernel linux-image-2.6.29-2-686 > > 2.6.29-5. > > > > Do you have any other idea what we can try? > > > > Did you try a 2.6.30-rc* kernel? Some packages are available at > http://kernel-archive.buildserver.net/debian-kernel/ linux-image-2.6.30-rc8-686 fixed my problem. /proc/mtrr now looks like: reg00: base=0x0 (0MB), size= 256MB, count=1: write-back reg01: base=0x00ff0 ( 255MB), size=1MB, count=1: uncachable reg02: base=0x0f000 ( 3840MB), size= 128MB, count=2: write-combining I had: 2.6.28: reg00: base=0x0 (0MB), size= 1024MB, count=1: write-back reg01: base=0x03ff0 ( 1023MB), size=1MB, count=1: uncachable /proc/mtrr in 2.6.29: reg00: base=0x0 (0MB), size= 1024MB, count=1: write-back reg01: base=0x03ff0 ( 1023MB), size=1MB, count=1: uncachable reg02: base=0x0e800 ( 3712MB), size= 128MB, count=2: write-combining Notice the 1024 MB changed to 256 MB. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#523415: corrupted rendering
On Thu, Apr 16, 2009 at 10:38:43PM +0200, Brice Goglin wrote: > Kurt Roeckx wrote: > > > > That removes the line, but does not solve the problem. > > > > Right, removing write-combining is only supposed to decrease performance :) So I'm still seeing this problem with the latest version in unstable (2:2.7.1-1) and kernel linux-image-2.6.29-2-686 2.6.29-5. Do you have any other idea what we can try? Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#531294: x11-common: dpkg: warning: obsolete option '--print-installation-architecture'
Package: x11-common Version: 1:7.4+1 Hi, I'm seeing this message now when installing pacakges: Unpacking x11-common (from .../x11-common_1%3a7.4+1_all.deb) ... dpkg: warning: obsolete option '--print-installation-architecture', please use '--print-architecture' instead. dpkg: warning: obsolete option '--print-installation-architecture', please use '--print-architecture' instead. [...] Setting up x11-common (1:7.4+1) ... dpkg: warning: obsolete option '--print-installation-architecture', please use '--print-architecture' instead. dpkg: warning: obsolete option '--print-installation-architecture', please use '--print-architecture' instead. All runlevel operations denied by policy [...] Removing x11-common ... All runlevel operations denied by policy dpkg: warning: obsolete option '--print-installation-architecture', please use '--print-architecture' instead. Purging configuration files for x11-common ... dpkg: warning: obsolete option '--print-installation-architecture', please use '--print-architecture' instead. dpkg: warning: obsolete option '--print-installation-architecture', please use '--print-architecture' instead. I'm seeing this in almost every build log, and sbuild is sending me a separate mail with those warnings. So I would like it that you fix this soon. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#531295: libx11-6: warning: obsolete option '--print-installation-architecture'
Package: libx11-6 Version: 2:1.2.1-1 Hi, I'm seeing this: Unpacking libx11-6 (from .../libx11-6_2%3a1.2.1-1_amd64.deb) ... dpkg: warning: obsolete option '--print-installation-architecture', please use '--print-architecture' instead. I'm seeing this in almost every build log, and sbuild is sending me a separate mail with those warnings. So I would like it that that this gets fixed soon. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#523415: corrupted rendering
On Thu, Apr 16, 2009 at 08:48:54PM +0200, Brice Goglin wrote: > Kurt Roeckx wrote: > > On Thu, Apr 16, 2009 at 08:09:30PM +0200, Frederic Peters wrote: > > > >> Brice Goglin wrote: > >> > >> > >>> So now, booting 2.6.29 and doing as root > >>> echo "base=0x0e800 size=0x800 type=write-combining" > > >>> /proc/mtrr > >>> might give you the same MTRR back, and might even fix your problems. > >>> > >> Same corrupted display for me after updating MTRR, too bad :( > >> > > > > I was under the impression that 2.6.29 already had this, and > > 2.6.28 didn't. So that would mean you would have to remove it > > in 2.6.29, and I have no idea if you can do that, and how. > > > > echo disable=2 > /proc/mtrr That removes the line, but does not solve the problem. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#523415: corrupted rendering
On Thu, Apr 16, 2009 at 08:09:30PM +0200, Frederic Peters wrote: > Brice Goglin wrote: > > > So now, booting 2.6.29 and doing as root > > echo "base=0x0e800 size=0x800 type=write-combining" > /proc/mtrr > > might give you the same MTRR back, and might even fix your problems. > > Same corrupted display for me after updating MTRR, too bad :( I was under the impression that 2.6.29 already had this, and 2.6.28 didn't. So that would mean you would have to remove it in 2.6.29, and I have no idea if you can do that, and how. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#523415: corrupted rendering
On Wed, Apr 15, 2009 at 11:58:56PM +0200, Kurt Roeckx wrote: > On Sun, Apr 12, 2009 at 12:39:34PM +0200, Brice Goglin wrote: > > found 523415 2:2.6.99.903-1 > > I'm also seeing the same thing, but with a 830 chipset. Downgrading the kernel from 2.6.29 to 2.6.26 fixes the problem for me. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514791: libgl1-mesa-glx: segfault calling glGenLists();
On Sat, Feb 14, 2009 at 02:02:45PM +0100, Michel Dänzer wrote: > On Sat, 2009-02-14 at 13:29 +0100, Kurt Roeckx wrote: > > On Sat, Feb 14, 2009 at 12:27:29PM +0100, Michel Dänzer wrote: > > > On Fri, 2009-02-13 at 21:22 +0100, Kurt Roeckx wrote: > > > > > > > > If I use the 7.3 version, I still hit that breakpoint, but I > > > > do not get a segfault anymore, and everything appears to be > > > > working normally. > > > > > > Do you hit the glXMakeCurrent breakpoint in that case? Before or after > > > glGenLists or any other gl[^X]* function? > > > > I do not seem to hit any glX function at all, with either 7.0 or 7.3. > > That doesn't make any sense - there's no way to get any OpenGL rendering > on the screen without any glX functions getting called, certainly not > with libgl1-mesa-glx... > > Anyway, if you agree that this is more likely a bug in the application, > this report can be marked as notfound in 7.0 as well? Yes. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514791: libgl1-mesa-glx: segfault calling glGenLists();
On Sat, Feb 14, 2009 at 12:27:29PM +0100, Michel Dänzer wrote: > On Fri, 2009-02-13 at 21:22 +0100, Kurt Roeckx wrote: > > > > If I use the 7.3 version, I still hit that breakpoint, but I > > do not get a segfault anymore, and everything appears to be > > working normally. > > Do you hit the glXMakeCurrent breakpoint in that case? Before or after > glGenLists or any other gl[^X]* function? I do not seem to hit any glX function at all, with either 7.0 or 7.3. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514791: libgl1-mesa-glx: segfault calling glGenLists();
On Fri, Feb 13, 2009 at 08:50:20AM +0100, Michel D?nzer wrote: > On Thu, 2009-02-12 at 20:43 +0100, Kurt Roeckx wrote: > > On Thu, Feb 12, 2009 at 08:16:49PM +0100, Michel D?nzer wrote: > > > On Thu, 2009-02-12 at 19:36 +0100, Kurt Roeckx wrote: > > > > > > > > It does not call glXMakeCurrent at all. > > > > > > Then it could never work in a GLX environment. It doesn't call it > > > directly but probably via GLUT. > > > > Well, I never hit the breakpoint. > > Can you please provide a little more information? E.g., does the > glGenLists breakpoint get hit? Is this with the version of Mesa that > crashes? If not, does the program work? ... I was already happy with you stating it was a bug in icc examine, but if you really want more info. :) The glGenLists call is where the first problem in the software happens, and is the reason I made that small test program. If I comment out that part of the code, the next problem is the gl_font( FL_HELVETICA, 10 ); 2 lines lower. What I see with the 7.0 version of mesa is: - I see a border for the new window being drawn, but the canvas of it is transparent. - I hit the breakpoint - It segfaults Where the problem happens is this piece of assembler code from glapi_x86-64.S: #elif defined(PTHREADS) pushq %rdi call_x86_64_get_dispa...@plt popq%rdi movq40(%rax), %r11 jmp *%r11 I'm guessing that the %rax does not contain what is expected. I understand that the 7.3 version uses the TLS code instead, which might lead to the different behaviour. If I use the 7.3 version, I still hit that breakpoint, but I do not get a segfault anymore, and everything appears to be working normally. I did not try to build everything for i386, so I guess that the small test program working on i386 was just pure concidence. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514791: libgl1-mesa-glx: segfault calling glGenLists();
On Thu, Feb 12, 2009 at 08:16:49PM +0100, Michel D?nzer wrote: > On Thu, 2009-02-12 at 19:36 +0100, Kurt Roeckx wrote: > > On Thu, Feb 12, 2009 at 09:46:58AM +0100, Michel D?nzer wrote: > > > On Wed, 2009-02-11 at 18:44 +0100, Kurt Roeckx wrote: > > > > iccexamine works with the versions from experimental and segfaults > > > > with the version from testing/unstable. > > > > > > Your test program above is definitely incorrect, but that doesn't > > > necessarily mean anything for iccexamine. You could try running it in > > > gdb with breakpoints set on glXMakeCurrent and glGenLists. If the latter > > > is called before the former, iccexamine is broken. > > > > It does not call glXMakeCurrent at all. > > Then it could never work in a GLX environment. It doesn't call it > directly but probably via GLUT. Well, I never hit the breakpoint. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514395: LUT settings are not restored after switching to console.
forwarded 514395 https://bugs.freedesktop.org/show_bug.cgi?id=20088 thanks On Thu, Feb 12, 2009 at 11:31:20AM +0100, Michel D?nzer wrote: > On Wed, 2009-02-11 at 22:11 +0100, Kurt Roeckx wrote: > > On Wed, Feb 11, 2009 at 06:55:15PM +0100, Michel D?nzer wrote: > > I've tried using xgamma (from x11-xserver-utils 7.3+5) and then the setting > > are kept. xgamma uses the XF86VidModeSetGamma() call. > > > > I've rebuild dispwin so it uses the XF86VidModeSetGammaRamp() call instead > > and then the settings are also kept. > > AFAICT the driver RandR 1.2 code just sets the LUT values passed in by > the X server, so I'm reassigning. If this still happens with > xserver-xorg-core from experimental, you may want to report it upstream. So I've just reported it upstream. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514791: libgl1-mesa-glx: segfault calling glGenLists();
On Thu, Feb 12, 2009 at 09:46:58AM +0100, Michel D?nzer wrote: > On Wed, 2009-02-11 at 18:44 +0100, Kurt Roeckx wrote: > > iccexamine works with the versions from experimental and segfaults > > with the version from testing/unstable. > > Your test program above is definitely incorrect, but that doesn't > necessarily mean anything for iccexamine. You could try running it in > gdb with breakpoints set on glXMakeCurrent and glGenLists. If the latter > is called before the former, iccexamine is broken. It does not call glXMakeCurrent at all. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514395: LUT settings are not restored after switching to console.
On Wed, Feb 11, 2009 at 06:55:15PM +0100, Michel D?nzer wrote:
> On Wed, 2009-02-11 at 18:35 +0100, Kurt Roeckx wrote:
> > >
> > > > or atleast get them restored when switching back to X.
> > >
> > > What method does dispwin use for changing the LUT settings?
> >
> > It uses this for randr 1.2:
> > XRRCrtcGamma *crtcgam;
> >
> > debugr("Setting gamma using Randr 1.2\n");
> >
> > if ((crtcgam = XRRAllocGamma(r->nent)) == NULL) {
> > debugr(" XRRAllocGamma failed\n");
> > return 1;
> > }
> >
> > for (i = 0; i < r->nent; i++) {
> > crtcgam->red[i] = vals[0][i];
> > crtcgam->green[i] = vals[1][i];
> > crtcgam->blue[i] = vals[2][i];
> > }
> >
> > XRRSetCrtcGamma(p->mydisplay, p->crtc, crtcgam);
> > XSync(p->mydisplay, False); /* Flush the change
> > out */
> >
> > XRRFreeGamma(crtcgam);
> >
> > Else it would use XF86VidModeSetGammaRamp()
>
> At least with RandR 1.2, I suspect this could be an issue in the X
> server rather than the driver.
I've tried using xgamma (from x11-xserver-utils 7.3+5) and then the setting
are kept. xgamma uses the XF86VidModeSetGamma() call.
I've rebuild dispwin so it uses the XF86VidModeSetGammaRamp() call instead
and then the settings are also kept.
Kurt
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514791: libgl1-mesa-glx: segfault calling glGenLists();
On Wed, Feb 11, 2009 at 08:55:44AM +0100, Michel Dänzer wrote:
> On Tue, 2009-02-10 at 22:18 +0100, Kurt Roeckx wrote:
> > Package: libgl1-mesa-glx
> > Version: 7.0.3-7
> > Severity: important
> >
> > Hi,
> >
> > This little test program causes a segfault on amd64:
> > #include
> >
> > int main()
> > {
> > glGenLists(1);
> > return 0;
> > }
> >
> > But the same thing works with the version from experimental (7.3-1).
>
> That's purely luck; the result of calling GL functions is undefined
> without a current GLX context.
I was trying to use iccexamine which you can get at:
http://sourceforge.net/project/showfiles.php?group_id=177017&package_id=247078
But it has a few depedencies that aren't available Debian.
I have no idea how GLX works, I've never looked at it before.
iccexamine works with the versions from experimental and segfaults
with the version from testing/unstable.
Kurt
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514395: LUT settings are not restored after switching to console.
On Wed, Feb 11, 2009 at 10:30:30AM +0100, Michel Dänzer wrote:
> On Sat, 2009-02-07 at 01:37 +0100, Kurt Roeckx wrote:
> >
> > I'm using a tool called dispwin from the argyll packages (not yet in
> > Debian), to change the VideoLUT settings. This all works like it should.
> >
> > My problem now is that when I switch from X to console and then back to X
> > those settings are removed and not restored.
> >
> > I would either like to see them stay the way they are when switching
> > to the console,
>
> That's not really possible; the X driver is supposed to save and restore
> the console hardware state unmodified.
>
> > or atleast get them restored when switching back to X.
>
> What method does dispwin use for changing the LUT settings?
It uses this for randr 1.2:
XRRCrtcGamma *crtcgam;
debugr("Setting gamma using Randr 1.2\n");
if ((crtcgam = XRRAllocGamma(r->nent)) == NULL) {
debugr(" XRRAllocGamma failed\n");
return 1;
}
for (i = 0; i < r->nent; i++) {
crtcgam->red[i] = vals[0][i];
crtcgam->green[i] = vals[1][i];
crtcgam->blue[i] = vals[2][i];
}
XRRSetCrtcGamma(p->mydisplay, p->crtc, crtcgam);
XSync(p->mydisplay, False); /* Flush the change out
*/
XRRFreeGamma(crtcgam);
Else it would use XF86VidModeSetGammaRamp()
Kurt
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514791: libgl1-mesa-glx: segfault calling glGenLists();
Package: libgl1-mesa-glx
Version: 7.0.3-7
Severity: important
Hi,
This little test program causes a segfault on amd64:
#include
int main()
{
glGenLists(1);
return 0;
}
But the same thing works with the version from experimental (7.3-1).
Kurt
--
To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#514395: LUT settings are not restored after switching to console.
Package: xserver-xorg-video-radeon Version: 1:6.9.0-1+lenny4 Hi, I'm using a tool called dispwin from the argyll packages (not yet in Debian), to change the VideoLUT settings. This all works like it should. My problem now is that when I switch from X to console and then back to X those settings are removed and not restored. I would either like to see them stay the way they are when switching to the console, or atleast get them restored when switching back to X. Kurt -- To UNSUBSCRIBE, email to debian-x-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Bug#492099: xserver-xorg-video-glide: glide2 only available on i386.
Package: xserver-xorg-video-glide Version: 1.0.1-1 Hi, You're build depending on libglide2-dev which is only availableon i386, and have marked the packages as arch any. Can't you use libglide3-dev instead which is available on i386 alpha ia64 amd64? Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#418123: shoult not depend on xutils-dev
On Sat, Apr 07, 2007 at 12:10:32PM +0200, Brice Goglin wrote: > Russell Coker wrote: > > On Saturday 07 April 2007 17:46, Brice Goglin <[EMAIL PROTECTED]> > > wrote: > >>> xutils should not depend on xutils-dev. > >> I think it should, to ensure a smooth transition from sarge to etch. > >> xutils-dev did not exist in sarge. xutils used to contain all what's in > >> both xutils and xutils-dev now. > > > > In that case it should have been handled by a compatibility package. > > Well, this is a common example of package split. Transitional packages > only help when the new packages are not named as the old one. The only > way to satisfy people wanting a smooth upgrade from sarge, and not > installing xutils-dev unless required on a new Etch install would have > been to rename xutils into foo and foo-dev and add a transition package > xutils depending on foo and foo-dev. I am not sure this reason is enough > to justify a package renaming. > > Anyway, there's actually another bug report about this (#330751: xutils > package should be splitted). I'll keep this bug in my queue of things to > look at after Etch is released (it is unfortunately way too late for > Etch now). etch has been release, so as far as I can see, there is no longer a reason to keep this Depends. Could you either drop it, or change it to a Suggests or Recommends? Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#428794: kbd upgrade breaks keyboard driver
Hi, Can someone please tag this bug with a "found" version? It's currently set to affect all version upto 2:1.3.0.0.dfsg-8, so it says things like etch are affected, and I think it doesn't. I'm guessing it's some 2:1.2.0 version or something. If you can't really say it's a problem since some version, but it does not affect etch, please tag it with "lenny sid", so that the bts will think it's fixed in all versions and can be archived. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366245: xserver-xorg-core: X crashes with Sig 11 when switching from console to GUI using Alt + Fn keys
tags 366245 fixed-upstream thanks On Mon, May 14, 2007 at 12:19:05AM +0200, Kurt Roeckx wrote: > > I saw it getting closed, so I tried the version from unstable. As a > result filed a different bug upstream: > https://bugs.freedesktop.org/show_bug.cgi?id=10937 > > At first look, I don't seem to have this problem anymore, but it's not > usable at all anymore now, so I can't really tell. So that upstream bugreport got closed too. I've just tried a current git version and everything seems to be working properly for me now. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366245: xserver-xorg-core: X crashes with Sig 11 when switching from console to GUI using Alt + Fn keys
On Mon, May 14, 2007 at 12:05:28AM +0200, Brice Goglin wrote: > > Hi, > > This bug about the X server crashing with the i810 driver when switching > from VT console back to X has been marked as fixed-upstream because the > upstream bug [1] got closed. Actually, this upstream bug is only marked > as "invalid" with reason "please test with intel driver 2.0". > > Could you guys please report back whether you can reproduce the problem > with xserver-xorg-video-intel 2.0 and xserver-xorg-core 1.3 (currently > in unstable)? If it still crashes, feel free to reopen [1] and add > comments (or ask me to do so). I saw it getting closed, so I tried the version from unstable. As a result filed a different bug upstream: https://bugs.freedesktop.org/show_bug.cgi?id=10937 (There seem to be a few simular but different problems.) At first look, I don't seem to have this problem anymore, but it's not usable at all anymore now, so I can't really tell. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#386028: xserver-xorg-video-tdfx: Characters corrupted when switching to console.
found 386028 1:1.3.0-1 thanks On Sat, May 05, 2007 at 12:05:42AM +0200, Brice Goglin wrote: > Hi, > > About a year ago, you reported a bug to the Debian BTS regarding > character corruption when switching to console on a 3dfx board. Did you > reproduce this problem recently? With Xorg/Etch? If not, I will close > this bug in the next weeks. This is still perfectly reproducible in etch. I've even tried without drm enabled now. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#419581: xvfb-run: Should depend on xbase-clients: xauth command not found
On Mon, Apr 16, 2007 at 02:03:43PM -0700, Martin Michlmayr wrote: > * Kurt Roeckx <[EMAIL PROTECTED]> [2007-04-16 20:44]: > > Package: xvfb-run > > Is this a typo? I cannot see this in Debian nor in incoming. Yes, already reassigned myself. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#418298: xserver-xorg-video-ati: doesn't set numlock led back when switching to console and back.
Package: xserver-xorg-video-ati Version: 6.6.3-2 Hi, It seems that if I switch from X to console and back to X, my numlock led goes out, but numlock is still enabled and I need to press the numlock key twice to get it back on. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366245: X crashes with Sig 11 when switching from console to+GUI using Alt + Fn keys
On Mon, Dec 25, 2006 at 04:31:46PM +0100, Kurt Roeckx wrote: > > All I get from this is, that it seems to have had a 2 second timeout. > I have no idea from which point it starts to count those 2 seconds. > > What I notice when switching is that it does take some time before it > actually redraws the screen, and that might be in the order of 2 seconds. > > What I always notice when it's crashing is that it only draws the bottom > half of the screen, and the upper half is black. > > I'm going to try with a higher timeout, and see what results this gives. > This seems like a good candidate, since it's timing related, not everybody > has the problem, and I might have a slower machine. So, this didn't help at all, and just seemt have as effect that when it goes wrong, it now still seems be responsive for a while, and then give the error. What i notice when it works is that the screen is mostly something close to white, except the top 80 lines. There is also a white square also about 80 lines or something lower then where it ends up after it has properly redrawn it. When it fails, it already already has the bottom half of the screen, but about 80 lines lower than it should be, top half is black, except the top 80 lines or something, which look about the same as when it works. It then just seems to move everything up 80 lines, and then it hangs. Just before it hangs, and the top half is black, with the delay that I changed, I can perfectly move the mouse into that top half and it properly shows it, but that's probably normal. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#366245: X crashes with Sig 11 when switching from console to+GUI using Alt + Fn keys
On Sat, Dec 23, 2006 at 02:31:56PM -0500, David Nusinow wrote:
>
> That said, let's try to actually fix the problem. The best thing to do
> would be to get a full backtrace. You'll want to build the server and
> driver with debugging symbols enabled. These are stock debhelper packages,
> so building with DEB_BUILD_OPTIONS set to nostrip (as per dh_strip(1)) will
> work. Then if you follow the basic instructions at
> http://wiki.x.org/wiki/DebuggingTheXserver you can get the backtraces. We
> should be able to go from there. Sorry we don't have -dbg packages, but
> several people vetoed them as archive bloat, although I'll probably be
> making a server one for etch.
It seems be much harder to reproduce when gdb is attached.
All I get from this is, that it seems to have had a 2 second timeout.
I have no idea from which point it starts to count those 2 seconds.
What I notice when switching is that it does take some time before it
actually redraws the screen, and that might be in the order of 2 seconds.
What I always notice when it's crashing is that it only draws the bottom
half of the screen, and the upper half is black.
I'm going to try with a higher timeout, and see what results this gives.
This seems like a good candidate, since it's timing related, not everybody
has the problem, and I might have a slower machine.
Anyway, I finally got a stack trace:
#0 0xb7f3a410 in ?? ()
#1 0xbfc2589c in ?? ()
#2 0x0006 in ?? ()
#3 0x0bc1 in ?? ()
#4 0xb7d51811 in raise () from /lib/tls/i686/cmov/libc.so.6
#5 0xb7d52fb9 in abort () from /lib/tls/i686/cmov/libc.so.6
#6 0x081a299c in FatalError (f=0xb7bbc6fc "lockup\n") at ../../os/log.c:556
#7 0xb7b8f83c in I830WaitLpRing (pScrn=0x81fd0d8, n=131064,
timeout_millis=2000) at ../../src/i830_accel.c:115
#8 0xb7b90092 in I830Sync (pScrn=0x81fd0d8) at ../../src/i830_accel.c:166
#9 0xb79bfe2d in XAALeaveVT () from /usr/lib/xorg/modules/libxaa.so
#10 0x080d7e79 in xf86XVLeaveVT (index=0, flags=0)
at ../../../../hw/xfree86/common/xf86xv.c:1278
#11 0xb7c247cf in glxDRILeaveVT ()
from /usr/lib/xorg/modules/extensions/libglx.so
#12 0x0809f548 in AbortDDX () at ../../../../hw/xfree86/common/xf86Init.c:1308
#13 0x081a2473 in AbortServer () at ../../os/log.c:408
#14 0x081a2987 in FatalError (f=0xb7bbc6fc "lockup\n") at ../../os/log.c:554
#15 0xb7b8f83c in I830WaitLpRing (pScrn=0x81fd0d8, n=131064,
timeout_millis=2000) at ../../src/i830_accel.c:115
#16 0xb7b90092 in I830Sync (pScrn=0x81fd0d8) at ../../src/i830_accel.c:166
#17 0xb79c6502 in XAACopyAreaFallback () from /usr/lib/xorg/modules/libxaa.so
#18 0xb79c77f7 in XAACopyArea () from /usr/lib/xorg/modules/libxaa.so
#19 0x081566cd in damageCopyArea (pSrc=0x8397af8, pDst=0x8393b60,
pGC=0x8391e28, srcx=0, srcy=0, width=280, height=20, dstx=0, dsty=0)
at ../../../miext/damage/damage.c:790
#20 0x08084da9 in ProcCopyArea (client=0x835c360) at ../../dix/dispatch.c:1743
#21 0x08086cab in Dispatch () at ../../dix/dispatch.c:459
#22 0x0806e699 in main (argc=11, argv=0xbfc261f4, envp=0x0)
at ../../dix/main.c:479
(gdb) frame 6
#6 0x081a299c in FatalError (f=0xb7bbc6fc "lockup\n") at ../../os/log.c:556
556 abort();
(gdb) up
#7 0xb7b8f83c in I830WaitLpRing (pScrn=0x81fd0d8, n=131064,
timeout_millis=2000) at ../../src/i830_accel.c:115
115 FatalError("lockup\n");
(gdb) p last_head
$5 = 12
(gdb) p *ring
$7 = {tail_mask = 1, mem = {Start = -268374161, End = -268377405,
Size = -268374161, Physical = 4026593135, Offset = 4026597204,
Alignment = 4026564616, Key = -268374161, Pool = 0xf000fea5},
virtual_start = 0xf000e987 ,
head = -268374161, tail = -268374161, space = -268374161}
(gdb) p n
$8 = 131064
(gdb) up
#8 0xb7b90092 in I830Sync (pScrn=0x81fd0d8) at ../../src/i830_accel.c:166
166I830WaitLpRing(pScrn, pI830->LpRing->mem.Size - 8, 0);
(gdb) p pScrn
$17 = (ScrnInfoPtr) 0x81fd0d8
(gdb) p *pScrn
$19 = {driverVersion = 4000, driverName = 0xb7bbc87e "i810",
pScreen = 0x8201350, scrnIndex = 0, configured = 1, origIndex = 0,
imageByteOrder = 0, bitmapScanlineUnit = 32, bitmapScanlinePad = 32,
bitmapBitOrder = 0, numFormats = 0, formats = {{depth = 0 '\0',
bitsPerPixel = 0 '\0', scanlinePad = 0 '\0'}, {depth = 0 '\0',
bitsPerPixel = 0 '\0', scanlinePad = 0 '\0'}, {depth = 0 '\0',
bitsPerPixel = 0 '\0', scanlinePad = 0 '\0'}, {depth = 0 '\0',
bitsPerPixel = 0 '\0', scanlinePad = 0 '\0'}, {depth = 0 '\0',
bitsPerPixel = 0 '\0', scanlinePad = 0 '\0'}, {depth = 0 '\0',
bitsPerPixel = 0 '\0', scanlinePad = 0 '\0'}, {depth = 0 '\0',
bitsPerPixel = 0 '\0', scanlinePad = 0 '\0'}, {depth = 0 '\0',
bitsPerPixel = 0 '\0', scanlinePad = 0 '\0'}}, fbFormat = {
depth = 16 '\020', bitsPerPixel = 16 '\020', scanlinePad = 32 ' '},
bitsPerPixel = 16, pixmap24 = Pix24DontCare, depth = 16,
depthFrom = X_CONFIG, bitsPerPixelFrom = X_PROBED, weight = {red = 5,
green = 6, blue = 5}, mask = {red = 63488, green = 20
Bug#366245: X crashes with Sig 11 when switching from console to+GUI using Alt + Fn keys
Hi, I've seen that you've set the severity to important again. Can you please explain why? Why i think this should have a higher severity is: - X crashed at something that I consider to be a normal use case. - When it crashes, you basicly can't use the computer anymore and it needs to be restarted the hard way. - I'm not the only having the problem. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#386028: xserver-xorg-video-tdfx: Characters corrupted when switching to console.
Package: xserver-xorg-video-tdfx Version: 1:1.1.1.3-3 Hi, I have a voodoo banshee card, and when I switch between X and the console, which is on a framebuffer, I ussually have 1 character that is slightly corrupted. Switching to X again and back to the console might fix it, it might stay, or it might be an other character that has the problem. I ussually only see the the character half, the upper lines are ussually there, but the lower not. It's not always the same amount of lines that I see. I have no idea what really happens, but I assume that when switching back to the console, X (or the kernel?) is putting back the font for the console/framebuffer, and that it doesn't always do it properly. My guess would be some race condition, since it's not always the same character that has the problem. Note that this is not really a new problem, I used to have this with xfree86 too, I just never filed a bug about it or really looked at it before. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362036: libx11-dev should not depend on libxi-dev
On Tue, Apr 11, 2006 at 11:49:10PM +0200, Kurt Roeckx wrote: > found 362036 2:1.0.0-5 > thanks > > I forgot to set the version. > > The changelog for 2:1.0.0-4 said that it was fixed, but looking > at it, it didn't get fixed. > > Anyway, there is an other circular build dependency between > libxkbfile-dev and libx11-dev. > > libx11-dev should probably not depend on libxkbfile-dev either. It looks like that needs to get changed to x11proto-kb. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362036: libx11-dev should not depend on libxi-dev
found 362036 2:1.0.0-5 thanks I forgot to set the version. The changelog for 2:1.0.0-4 said that it was fixed, but looking at it, it didn't get fixed. Anyway, there is an other circular build dependency between libxkbfile-dev and libx11-dev. libx11-dev should probably not depend on libxkbfile-dev either. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#362036: libx11-dev should not depend on libxi-dev
Package: libx11-dev Version: Severity: serious Hi, As discussed in #356918, libx11-dev should not depend on libxi-dev but on x11proto-input-dev instead. It said it was commited to svn, but it doesn't seem to have made it to the package. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#359023: xterm: Xft support missing on amd64
Hi, A binNMU has been scheduled on amd64 for this problem, so the bug should go away. But someone will need to verify that it actually works now. It would also be a good idea if it actually failed to build in case it can't find the Xft header files. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Fixed in NMU of xft 2.1.8.2-5.1
tag 358665 + fixed quit This message was generated automatically in response to a non-maintainer upload. The .changes file follows. -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Format: 1.7 Date: Thu, 23 Mar 2006 21:07:01 +0100 Source: xft Binary: libxft-dev libxft2 libxft2-dbg Architecture: source i386 Version: 2.1.8.2-5.1 Distribution: unstable Urgency: low Maintainer: Debian X Strike Force Changed-By: Kurt Roeckx <[EMAIL PROTECTED]> Description: libxft-dev - FreeType-based font drawing library for X (development files) libxft2- FreeType-based font drawing library for X libxft2-dbg - FreeType-based font drawing library for X (unstripped) Closes: 358665 Changes: xft (2.1.8.2-5.1) unstable; urgency=low . * Non-maintainer upload. * Install header files in /usr/X11R6/include/X11/Xft (Closes: #358665) Files: be8b6697fef5e7e8b546844a434e2cbe 792 devel optional xft_2.1.8.2-5.1.dsc 374fc151ba3a948257b3d35c6f051eb2 20755 devel optional xft_2.1.8.2-5.1.diff.gz 930fdbb7d00dac982cb26f00581594cf 44078 libs optional libxft2_2.1.8.2-5.1_i386.deb 41d0177c015d4360133cc6b270f9cf2b 8736 libdevel extra libxft2-dbg_2.1.8.2-5.1_i386.deb 52ec60c20babc6aaab67b9ce8bdad03e 57072 libdevel optional libxft-dev_2.1.8.2-5.1_i386.deb -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.2.2 (GNU/Linux) iD8DBQFEIwCjQdwckHJElwsRAtHcAJ48MAYnw6EQIslQhqCa8nTfZdkHmwCfWPkL 8+p9IrhvTl0gEeM5shh81po= =s3ky -END PGP SIGNATURE- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#358665: xft: Wrong dir for include directory.
On Thu, Mar 23, 2006 at 08:17:30PM +0100, Kurt Roeckx wrote: > > It seems you have moved the include files to: > /usr/X11R6/include/Xft > > Which is wrong, and now everything that needs them is failing to > build. > > It should be: > /usr/X11R6/include/X11/Xft I've just NMU'd this, patch is attached. Kurt diff -u xft-2.1.8.2/debian/changelog xft-2.1.8.2/debian/changelog --- xft-2.1.8.2/debian/changelog +++ xft-2.1.8.2/debian/changelog @@ -1,3 +1,11 @@ +xft (2.1.8.2-5.1) unstable; urgency=low + + * Non-maintainer upload. + * Install header files in /usr/X11R6/include/X11/Xft + (Closes: #358665) + + -- Kurt Roeckx <[EMAIL PROTECTED]> Thu, 23 Mar 2006 21:07:01 +0100 + xft (2.1.8.2-5) unstable; urgency=low * Actually install the header files to /usr/X11R6/include/Xft. Thanks Steve diff -u xft-2.1.8.2/debian/libxft-dev.install xft-2.1.8.2/debian/libxft-dev.install --- xft-2.1.8.2/debian/libxft-dev.install +++ xft-2.1.8.2/debian/libxft-dev.install @@ -1,5 +1,5 @@ -usr/include/X11/Xft/Xft.h usr/X11R6/include/Xft -usr/include/X11/Xft/XftCompat.h usr/X11R6/include/Xft +usr/include/X11/Xft/Xft.h usr/X11R6/include/X11/Xft +usr/include/X11/Xft/XftCompat.h usr/X11R6/include/X11/Xft usr/lib/libXft.a usr/lib/libXft.so usr/lib/pkgconfig/*.pc
Bug#358665: xft: Wrong dir for include directory.
Package: xft Version: 2.1.8.2-5 Severity: serious Hi, It seems you have moved the include files to: /usr/X11R6/include/Xft Which is wrong, and now everything that needs them is failing to build. It should be: /usr/X11R6/include/X11/Xft It would be nice if this could be uploaded soon. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351779: x.org r6 and r7 don't play nice together yet
On Sun, Mar 19, 2006 at 08:51:52PM +0100, Kurt Roeckx wrote: > Atleast for xtrans-dev 1.0.0-2 this hasn't been fixed yet. So do the following: x11proto-core-dev libxdmcp-dev Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#351779: x.org r6 and r7 don't play nice together yet
Atleast for xtrans-dev 1.0.0-2 this hasn't been fixed yet. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#356918: libx11: FTBFS in experimental.
On Tue, Mar 14, 2006 at 11:50:34PM +0100, Denis Barbier wrote: > On Tue, Mar 14, 2006 at 11:03:32PM +0100, Kurt Roeckx wrote: > > Anyway, the package checks for a "inputproto.pc" file directly. > > It doesn't check for xextproto.pc (at that point), and libxi-dev > > doesn't even contain a .pc file. So you should build depend on > > it directly too. > > I know nothing about pkg-config and won't fix this stuff myself, but > just to clarify, configure.ac contains > PKG_CHECK_MODULES(X11, xextproto xtrans xau xcmiscproto) > which is surely why there is this dependency on x11proto-xext-dev. Yes, but later there is: AM_CONDITIONAL(XKB, [ test x$XKB = xyes ]) if test x"$XKB" = "xyes"; then XKBPROTO_REQUIRES="kbproto inputproto" PKG_CHECK_MODULES(XKBPROTO, $XKBPROTO_REQUIRES) PS: I would be happy with the proposed patch, as now libxi-dev and libx11-dev depend on each other, which really isn't something you want. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#356918: libx11: FTBFS in experimental.
On Tue, Mar 14, 2006 at 10:49:50PM +0100, Denis Barbier wrote: > On Tue, Mar 14, 2006 at 07:49:42PM +0100, Kurt Roeckx wrote: > > Package: libx11 > > Version: 1:1.0.0-3 > > Severity: serious > > Tags: serious > > > > Hi, > > > > Your package is still failing to build. First I get: > > checking for XKBPROTO... configure: error: Package requirements > [...] > > Which seems to be a missing build dependency on > > x11proto-input-dev. > > This dependency does exist: > x11proto-xext-dev --> libxi-dev --> x11proto-input-dev Not for the libxi-dev from unstable. Anyway, the package checks for a "inputproto.pc" file directly. It doesn't check for xextproto.pc (at that point), and libxi-dev doesn't even contain a .pc file. So you should build depend on it directly too. I see no need to make the x11proto-xext-dev depedency on libxi-dev versioned, so I suggest you don't do it. > OTOH quilt is missing. But that doesn't seem to be required to build the package. Atleast, it's just giving an error during clean which gets ignored, so I ignored that too, and looks like I shouldn't. > > Then I get: > > Making all in ru_RU.UTF-8 > > make[3]: Entering directory > > `/usr/src/libx11-1.0.0/obj-x86_64-linux-gnu/nls/ru_RU.UTF-8' > > make[3]: *** No rule to make target `XI18N_OBJS', needed by `all-am'. Stop. > > make[3]: Leaving directory > > `/usr/src/libx11-1.0.0/obj-x86_64-linux-gnu/nls/ru_RU.UTF-8' > > make[2]: *** [all-recursive] Error 1 > > > > I wonder why I didn't get any of those errors the previous time > > though. > > It looks fine with current SVN. Installing quilt seems to fix it. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#356918: libx11: FTBFS in experimental.
Package: libx11 Version: 1:1.0.0-3 Severity: serious Tags: serious Hi, Your package is still failing to build. First I get: checking for XKBPROTO... configure: error: Package requirements (kbproto inputproto) were not met: No package 'inputproto' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables XKBPROTO_CFLAGS and XKBPROTO_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** [build-stamp] Error 1 Which seems to be a missing build dependency on x11proto-input-dev. Then I get: Making all in ru_RU.UTF-8 make[3]: Entering directory `/usr/src/libx11-1.0.0/obj-x86_64-linux-gnu/nls/ru_RU.UTF-8' make[3]: *** No rule to make target `XI18N_OBJS', needed by `all-am'. Stop. make[3]: Leaving directory `/usr/src/libx11-1.0.0/obj-x86_64-linux-gnu/nls/ru_RU.UTF-8' make[2]: *** [all-recursive] Error 1 I wonder why I didn't get any of those errors the previous time though. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#354099: xdm_1:1.0.1-1: FTBFS: configure error
The problem is that the build dependency say: libxmu-dev (>= 1.0.1-1), libx11-dev (>= 1.0.0-1), libxau-dev (>= 1.0.0-1), libxaw7-dev (>= 1.0.1-1) libxmu-dev doesn't seem to have a source package in experimental (yet?), but I assume it's having the same problems as all the others. The others are all missing the epoch in the version, and should says: libx11-dev (>= 1:1.0.0-1), libxau-dev (>= 1:1.0.0-1), libxaw7-dev (>= 1:1.0.1-1) Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#356421: xutils: FTBFS: Missing version for build dependencies.
Package: xutils Version: 1:1.0.1-1 Severity: serious Tags: experimental Hi, Your package is failing to build with the following error: checking pkg-config is at least version 0.9.0... yes checking for FSLSFONTS... configure: error: Package requirements (x11 libfs) were not met: No package 'x11' found No package 'libfs' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables FSLSFONTS_CFLAGS and FSLSFONTS_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** [build-stamp] Error 1 It seems both libx11-dev and libfs-dev are missing the version requirements to build it. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#356420: xfonts-utils: FTBFS: Missing build dependency.
Package: xfonts-utils Version: 1:1.0.0-1 Severity: serious Hi, Your package is failing to build with the following error: checking for X11... configure: error: Package requirements (x11) were not met: No package 'x11' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables X11_CFLAGS and X11_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** [build-stamp] Error 1 This looks like a missing build dependency on libx11-dev (>= 1:1.0.0) Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#356415: libx11-6: Should conflict with (old) xlibs-data
Package: libx11-6 Version: 1.0.0-1 Severity: serious Hi, It seems there is a conflict between libx11-6 and xlibs-data: Unpacking xlibs-data (from .../xlibs-data_6.9.0.dfsg.1-4_all.deb) ... dpkg: error processing /var/cache/apt/archives/xlibs-data_6.9.0.dfsg.1-4_all.deb (--unpack): trying to overwrite `/usr/X11R6/lib/X11/locale', which is also in package libx11-6 dpkg-deb: subprocess paste killed by signal (Broken pipe) Errors were encountered while processing: /var/cache/apt/archives/xlibs-data_6.9.0.dfsg.1-4_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) Also, I don't think you can replace a directory by a symlink. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#354167: libxext: FTBFS in experimental: Missing build dependency.
reassign 354167 libx11-dev 1.0.0-1 thanks On Thu, Feb 23, 2006 at 09:49:42PM +0100, Kurt Roeckx wrote: > This seems to be a missing build dependency on > x11proto-input-dev. > > It also can't find the xdmcp.pc, which looks like a missing build > dependency on libxdmcp-dev, but please make sure it has a > version requirement to have a version with a .pc file in it. Both actually seem to be missing depedencies of libx11-dev. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#354165: x11proto-core-dev: Wrong version requirement for x11-common.
merge 351779 354165 thanks Looks like they're the same, and I seem to have picked the same random one as Frank to report it against. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#354167: libxext: FTBFS in experimental: Missing build dependency.
Package: libxext Version: 1:1.0.0-1 Severity: serious Tags: experimental Hi, Your package is failing to build with the following error: checking for XEXT... configure: error: Package requirements (xproto x11 xextproto xau) were not met: Package inputproto was not found in the pkg-config search path. Perhaps you should add the directory containing `inputproto.pc' to the PKG_CONFIG_PATH environment variable Package 'inputproto', required by 'X11', not found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables XEXT_CFLAGS and XEXT_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** [build-stamp] Error 1 This seems to be a missing build dependency on x11proto-input-dev. It also can't find the xdmcp.pc, which looks like a missing build dependency on libxdmcp-dev, but please make sure it has a version requirement to have a version with a .pc file in it. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#354165: x11proto-core-dev: Wrong version requirement for x11-common.
Package: x11proto-core-dev Version: 7.0.4-1 Severity: serious Hi, You have a lot of packages with a Pre-Dependency on x11-common, but all with the wrong version. It says things like: Pre-Depends: x11-common (>= 0.99) Or: Pre-Depends: x11-common (>= 1.0) Which can be satisfied by 6.9.0.dfsg.1-4. It should be using 1:1.0 instead. Could you please fix this in all the packages without me having to submit a bug to each package? Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#354161: libx11: FTBFS in experimental: Missing .pc files.
Package: libx11 Version: 2:1.0.0-1 Severity: serious Tags: experimental Hi, Your package is failing to build with the following error: checking for BIGREQS... yes checking for XPROTO... yes checking for X11... configure: error: Package requirements (xextproto xtrans xau xcmiscproto) were not met: No package 'xau' found Consider adjusting the PKG_CONFIG_PATH environment variable if you installed software in a non-standard prefix. Alternatively, you may set the environment variables X11_CFLAGS and X11_LIBS to avoid the need to call pkg-config. See the pkg-config man page for more details. make: *** [build-stamp] Error 1 libxau-dev is installed, and is version 6.9.0.dfsg.1-4, but it seems to need a .pc file, which only seems to be present in 1:1.0.0. It seems you need to require atleast the following versions: libxau-dev (>= 1:1.0.0) libxdmcp-dev (>= 1:1.0.0) (This has still some other 6.9 version installed, but seems to build without problems with those.) Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345387: tries to overweite stuff in xlibs; missing Replaces:?
On Sun, Jan 01, 2006 at 11:25:02PM +, Stephen Gran wrote: > This one time, at band camp, Kurt Roeckx said: > > xlibs should get removed, so I think it should be a Conflicts. > > Surely nothing so drastic as removing xlibs is necessary for moving a > file between packages? The versioned conflicts/replaces/etc magic is > probably all that's necessary. xlibs is a transitional package that should get removed in the 6.9.0.dfsg.1-2 version. The binary package shouldn't exist at all anymore. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#343822: xorg-x11: FTBFS: manifest differences
found 343822 6.9.0.dfsg.1-1 thanks Hi, It's still failing on amd64 with the following error: --- debian/MANIFEST.amd64 2005-12-31 04:14:49.0 +0100 +++ debian/MANIFEST.amd64.new 2005-12-31 04:14:49.0 +0100 @@ -1157 +1156,0 @@ -usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html MANIFEST check failed; please see debian/README make: *** [stampdir/check-manifest] Error 1 Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#345387: tries to overweite stuff in xlibs; missing Replaces:?
On Sat, Dec 31, 2005 at 01:55:04AM +0100, Rene Engelhard wrote: > Package: xlibs-data > Version: 6.9.0.dfsg.1-1 > Severity: serious > > Hi, > > on my just-ended dist-upgrade (sorry, german, but what happens should be > obvious, ask if not.. > > [...] > Vorbereiten zum Ersetzen von xlibs-data 6.8.2.dfsg.1-11 (durch > .../xlibs-data_6.9.0.dfsg.1-1_all.deb) ... > Entpacke Ersatz für xlibs-data ... > dpkg: Fehler beim Bearbeiten von > /var/cache/apt/archives/xlibs-data_6.9.0.dfsg.1-1_all.deb (--unpack): > versuche »/etc/X11/xkb/symbols/ar« zu überschreiben, welches auch in Paket > xlibs ist > dpkg-deb: Unterprozess paste getötet mit Signal (Datenübergabe unterbrochen > (broken pipe)) > Vorbereiten zum Ersetzen von xlibs 6.8.2.dfsg.1-11 (durch > .../xlibs_6.9.0.dfsg.1-1_all.deb) ... > Entpacke Ersatz für xlibs ... > [...] I got the same thing: Preparing to replace xlibs-data 6.8.2.dfsg.1-11 (using .../xlibs-data_6.9.0.dfsg.1-1_all.deb) ... Unpacking replacement xlibs-data ... dpkg: error processing /var/cache/apt/archives/xlibs-data_6.9.0.dfsg.1-1_all.deb (--unpack): trying to overwrite `/etc/X11/xkb/symbols/ar', which is also in package xlibs dpkg-deb: subprocess paste killed by signal (Broken pipe) Preparing to replace xlibs 6.8.2.dfsg.1-11 (using .../xlibs_6.9.0.dfsg.1-1_all.deb) ... Unpacking replacement xlibs ... Preparing to replace xlibs-pic 6.8.2.dfsg.1-11 (using .../xlibs-pic_6.9.0.dfsg.1-1_all.deb) ... Unpacking replacement xlibs-pic ... Errors were encountered while processing: /var/cache/apt/archives/xlibs-data_6.9.0.dfsg.1-1_all.deb E: Sub-process /usr/bin/dpkg returned an error code (1) xlibs should get removed, so I think it should be a Conflicts. Kurt
Bug#343822: xorg-x11: FTBFS: manifest differences
Package: xorg-x11 Version: 6.8.99.903.dfsg.1-1 Severity: serious Tags: experimental Hi, Your package is failing to build on amd64 with the following error: --- debian/MANIFEST.amd64 2005-12-17 22:22:20.0 +0100 +++ debian/MANIFEST.amd64.new 2005-12-17 22:22:20.0 +0100 @@ -479 +478,0 @@ -usr/X11R6/bin/pclcomp @@ -1158 +1156,0 @@ -usr/X11R6/lib/X11/doc/html/Xprint_FAQ.html @@ -1743 +1740,0 @@ -usr/X11R6/man/man1/pclcomp.1x MANIFEST check failed; please see debian/README make: *** [stampdir/check-manifest] Error 1 I think this applies to more than just amd64, since it seems to have been removed for being non-free, and other manifest files still mention it. I'm not sure about the Xprint_FAQ.html though. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#332839: xorg-x11: FTBFS on amd64: manifest changed.
Package: xorg-x11 Version: 6.8.99.900.dfsg.1-0pre1 Severity: important Tags: experimental Hi, Your package is failing to build on amd64 because the manifest changed. Please find the diff attached. The new file seems to look alot like the MANIFEST.i386.in file, and I guess that changed in the last upload? Kurt --- debian/MANIFEST.amd64 2005-10-08 23:13:02.0 +0200 +++ debian/MANIFEST.amd64.new 2005-10-08 23:13:02.0 +0200 @@ -18,2 +17,0 @@ -etc/X11/app-defaults/KOI8RXTerm -etc/X11/app-defaults/UXTerm @@ -34,2 +31,0 @@ -etc/X11/app-defaults/XTerm -etc/X11/app-defaults/XTerm-color @@ -455 +450,0 @@ -usr/X11R6/bin/Xorg-debug @@ -470,2 +464,0 @@ -usr/X11R6/bin/dpsexec -usr/X11R6/bin/dpsinfo @@ -485 +477,0 @@ -usr/X11R6/bin/koi8rxterm @@ -490 +481,0 @@ -usr/X11R6/bin/lxterm @@ -493 +483,0 @@ -usr/X11R6/bin/makepsres @@ -504,0 +495 @@ +usr/X11R6/bin/pclcomp @@ -506,2 +496,0 @@ -usr/X11R6/bin/pswrap -usr/X11R6/bin/resize @@ -520 +508,0 @@ -usr/X11R6/bin/texteroids @@ -523 +510,0 @@ -usr/X11R6/bin/uxterm @@ -528,0 +516 @@ +usr/X11R6/bin/xauth_switch_to_sun-des-1 @@ -536,0 +525 @@ +usr/X11R6/bin/xdbedizzy @@ -539,0 +529 @@ +usr/X11R6/bin/xdpr @@ -577,0 +568 @@ +usr/X11R6/bin/xpr @@ -591 +581,0 @@ -usr/X11R6/bin/xterm @@ -604,26 +593,0 @@ -usr/X11R6/include/DPS/ColorSB.h -usr/X11R6/include/DPS/ColorSBP.h -usr/X11R6/include/DPS/DPSScrollW.h -usr/X11R6/include/DPS/DPSScrollWP.h -usr/X11R6/include/DPS/FontCreatP.h -usr/X11R6/include/DPS/FontCreato.h -usr/X11R6/include/DPS/FontSB.h -usr/X11R6/include/DPS/FontSBP.h -usr/X11R6/include/DPS/FontSamplP.h -usr/X11R6/include/DPS/FontSample.h -usr/X11R6/include/DPS/PSres.h -usr/X11R6/include/DPS/XDPS.h -usr/X11R6/include/DPS/XDPSlib.h -usr/X11R6/include/DPS/XDPSproto.h -usr/X11R6/include/DPS/dpsNXargs.h -usr/X11R6/include/DPS/dpsXclient.h -usr/X11R6/include/DPS/dpsXcommon.h -usr/X11R6/include/DPS/dpsXpreview.h -usr/X11R6/include/DPS/dpsXshare.h -usr/X11R6/include/DPS/dpsXuserpath.h -usr/X11R6/include/DPS/dpsclient.h -usr/X11R6/include/DPS/dpsconfig.h -usr/X11R6/include/DPS/dpsexcept.h -usr/X11R6/include/DPS/dpsfriends.h -usr/X11R6/include/DPS/dpsops.h -usr/X11R6/include/DPS/psops.h @@ -643,0 +608 @@ +usr/X11R6/include/X11/CallbackI.h @@ -647,0 +613 @@ +usr/X11R6/include/X11/ConvertI.h @@ -649,0 +616 @@ +usr/X11R6/include/X11/CreateI.h @@ -650,0 +618 @@ +usr/X11R6/include/X11/EventI.h @@ -651,0 +620 @@ +usr/X11R6/include/X11/HookObjI.h @@ -657,0 +627,2 @@ +usr/X11R6/include/X11/ImUtil.h +usr/X11R6/include/X11/InitialI.h @@ -658,0 +630 @@ +usr/X11R6/include/X11/IntrinsicI.h @@ -663,0 +636 @@ +usr/X11R6/include/X11/PassivGraI.h @@ -665,0 +639 @@ +usr/X11R6/include/X11/ResourceI.h @@ -668,0 +643 @@ +usr/X11R6/include/X11/SelectionI.h @@ -669,0 +645 @@ +usr/X11R6/include/X11/ShellI.h @@ -672,0 +649,3 @@ +usr/X11R6/include/X11/ThreadsI.h +usr/X11R6/include/X11/TranslateI.h +usr/X11R6/include/X11/VarargsI.h @@ -762,0 +742 @@ +usr/X11R6/include/X11/XlibConf.h @@ -795,0 +776 @@ +usr/X11R6/include/X11/Xregion.h @@ -981,0 +963 @@ +usr/X11R6/include/X11/extensions/vldXvMC.h @@ -1009,0 +992,7 @@ +usr/X11R6/include/X11/fonts/bdfint.h +usr/X11R6/include/X11/fonts/bitmap.h +usr/X11R6/include/X11/fonts/bufio.h +usr/X11R6/include/X11/fonts/fntfil.h +usr/X11R6/include/X11/fonts/fntfilio.h +usr/X11R6/include/X11/fonts/fntfilst.h +usr/X11R6/include/X11/fonts/font.h @@ -1010,0 +1000,7 @@ +usr/X11R6/include/X11/fonts/fontencc.h +usr/X11R6/include/X11/fonts/fontmisc.h +usr/X11R6/include/X11/fonts/fontmod.h +usr/X11R6/include/X11/fonts/fontshow.h +usr/X11R6/include/X11/fonts/fontstruct.h +usr/X11R6/include/X11/fonts/fontutil.h +usr/X11R6/include/X11/fonts/fontxlfd.h @@ -1011,0 +1008 @@ +usr/X11R6/include/X11/fonts/pcf.h @@ -1013,0 +1011,2 @@ +usr/X11R6/include/X11/misc.h +usr/X11R6/include/X11/os.h @@ -1028,0 +1028 @@ +usr/X11R6/lib/X11/config/DragonFly.cf @@ -1087,0 +1088,3 @@ +usr/X11R6/lib/X11/config/mingw.cf +usr/X11R6/lib/X11/config/mingw.rules +usr/X11R6/lib/X11/config/mingw.tmpl @@ -1175,2 +1177,0 @@ -usr/X11R6/lib/X11/etc/xterm.termcap -usr/X11R6/lib/X11/etc/xterm.terminfo @@ -1449,0 +1451,3 @@ +usr/X11R6/lib/X11/locale/zh_CN.gb18030/Compose +usr/X11R6/lib/X11/locale/zh_CN.gb18030/XI18N_OBJS +usr/X11R6/lib/X11/locale/zh_CN.gb18030/XLC_LOCALE @@ -1455,0 +1460,4 @@ +usr/X11R6/lib/X11/locale/zh_HK.UTF-8/XI18N_OBJS +usr/X11R6/lib/X11/locale/zh_HK.UTF-8/XLC_LOCALE +usr/X11R6/lib/X11/locale/zh_HK.big5/Compose +usr/X11R6/lib/X11/locale/zh_HK.big5/XI18N_OBJS @@ -1456,0 +1465 @@ +usr/X11R6/lib/X11/locale/zh_HK.big5hkscs/Compose @@ -1487,0 +1497 @@ +usr/X11R6/lib/X11/xorg.conf.eg @@ -1499 +1509 @@ -usr/X11R6/lib/libICE.so.6.3 +usr/X11R6/lib/libICE.so.6.4 @@ -1558,0 +1569,2 @@ +usr/X11R6/lib/libXvMCW.a +usr/X11R6/lib/libXvMCW.so.1.0 @@ -1569,4 +1580,0 @@ -usr/X11R6/lib/libdps.a -usr/X11R6/lib/libdps.so.1.0 -usr/X11R6/lib/libdpstk.a -usr/X11R6/lib/libdpstk.so.1.0 @@ -1576,2 +1584,4 @@ -usr/X11R6/lib/libpsres.a -usr/X11R6/lib/libpsres.so.1.0 +usr/X11R6/lib/libviaXvMC.a +usr/X11R6
Bug#323168: fixed in snmpkit 0.9-10
On Fri, Aug 19, 2005 at 02:18:13PM -0700, Debian Bug Tracking System wrote: > Changes: > snmpkit (0.9-10) unstable; urgency=low > . >* for some misterious reasons, the Conflict line that is in the source > did not reach the libsnmpkit2c2 deb ; so I am rebuilding it > (closes: #323168, #323488) That should have been #323138 and not #323168. Kurt -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Bug#240889: Build problem on amd64.
Package: xfree86 Version: 4.3.0-7 There are a few problem building on amd64: * It's missing a vars.amd64. I've copied vars.i386 * I get: XlcDL.c:64:4: #error "Unknown architecture" small patch: --- XlcDL.c.orig2004-03-29 13:30:49.659717577 -0600 +++ XlcDL.c 2004-03-29 10:58:24.0 -0600 @@ -58,7 +58,7 @@ #ifdef _LP64 # if defined(__sparcv9) # define _MACH64_NAME"sparcv9" -# elif defined(__ia64__) +# elif defined(__ia64__) || defined(__x86_64__) # undef MACH64_NAME # else # error "Unknown architecture" * In the control file there are some lines that limit the architectures and amd64 isn't on that list. Kurt
