This has occurred quite often for me as well in running the setup program.
I suspected a corrupt download (?!) and kept re-downloading a fresh copy
until one version finally worked. Didn't dig deep to find the root of the
problem, though.
---
Dan Chen [EMAIL PROTECTED]
GPG key: ww
The StarOffice 6.0 beta works just fine here on X 4.1.0[.1, it's a Debian
sid package, 4.1.0-9].
---
Dan Chen [EMAIL PROTECTED]
GPG key: www.cs.unc.edu/~chenda/pubkey.gpg.asc
On Sun, 28 Oct 2001, Papadakos Panagiotis wrote:
> There are problems with Xfree-4.1.0 and after.I don't
On Sun, 2001-10-28 at 02:02, Daryll Strauss wrote:
>
> I'm running Open Office 638 on XFree 4.1 just fine. Without more
> information as to what's happening when you try to run Star Office I
> don't think we can help you.
>
What do you need? An strace?
--
Gérard Milmeister
Tannenrauchstr. 35
8
I try to run setup from openoffice 638C and all I get is the message:
glibc version: 2.2.3 and then I get back to the shell.I am using the
latest CVS from Xfree and I am using a G400 Dualheaded.Also many other
people have the same problem,but nobody has explained why this is
happening.
On Sat, 2
Though I do not have either OpenOffice or StarOffice running, (I tried
OpenOffice, some problems) I do know that OpenOffice calls for libGL. I
would guess that your problem is in /etc/ld.so.conf You might want to
put /usr/X11R6/lib in front of /usr/X11R6-DRI/lib in that file.
Good luck,
Carl
On Sun, Oct 28, 2001 at 02:46:50AM +0300, Papadakos Panagiotis wrote:
> There are problems with Xfree-4.1.0 and after.I don't know what,but if you
> want tou use Openoffice-Staroffice 6.0 you will have to work with
> Xfree-4.0.3.
I'm running Open Office 638 on XFree 4.1 just fine. Without more
in
On Sun, 2001-10-28 at 01:46, Papadakos Panagiotis wrote:
> There are problems with Xfree-4.1.0 and after.I don't know what,but if you
> want tou use Openoffice-Staroffice 6.0 you will have to work with
> Xfree-4.0.3.
I found that the problem is with libXrender. If this
library is relocated SO sta
There are problems with Xfree-4.1.0 and after.I don't know what,but if you
want tou use Openoffice-Staroffice 6.0 you will have to work with
Xfree-4.0.3.
___
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-dev
OK, I actually looked at the definition of DRILock/DRIUnlock
(programs/Xserver/GL/dri/dri.c), and it does reference counting, so
locking twice might not be an issue, it just increments the reference
count. What I haven't found yet is where the DRM_LOCK/DRM_UNLOCK macros
used in DRILock/DRIUnlock
On Sat, 27 Oct 2001, Manuel Teira wrote:
> El Sáb 27 Oct 2001 21:40, Leif Delgass escribió:
> > On Sat, 27 Oct 2001, Manuel Teira wrote:
> > > El Sáb 27 Oct 2001 19:49, Leif Delgass escribió:
> > > > Well, I just got my box to hang hard (like with the vt switching) when
> > > > running tuxracer a
El Sáb 27 Oct 2001 21:40, Leif Delgass escribió:
> On Sat, 27 Oct 2001, Manuel Teira wrote:
> > El Sáb 27 Oct 2001 19:49, Leif Delgass escribió:
> > > Well, I just got my box to hang hard (like with the vt switching) when
> > > running tuxracer and switching modes with Ctrl-Alt-+ (I have 3 modes
>
On Sat, 27 Oct 2001, Manuel Teira wrote:
> El Sáb 27 Oct 2001 19:49, Leif Delgass escribió:
> > Well, I just got my box to hang hard (like with the vt switching) when
> > running tuxracer and switching modes with Ctrl-Alt-+ (I have 3 modes
> > defined in my config and the hang happened when loopi
El Sáb 27 Oct 2001 19:49, Leif Delgass escribió:
> Well, I just got my box to hang hard (like with the vt switching) when
> running tuxracer and switching modes with Ctrl-Alt-+ (I have 3 modes
> defined in my config and the hang happened when looping back to the
> original mode, i.e. the third swi
Well, I just got my box to hang hard (like with the vt switching) when
running tuxracer and switching modes with Ctrl-Alt-+ (I have 3 modes
defined in my config and the hang happened when looping back to the
original mode, i.e. the third switch), so I think the
answer is yes, it needs locking.
El Sáb 27 Oct 2001 18:49, Leif Delgass escribió:
> First off, I messed up on the FIFO size defines in mach64_drv.h (drm
> kernel module), they should be:
>
> # define MACH64_CMDFIFO_SIZE_MASK 0x0003ul
> # define MACH64_CMDFIFO_SIZE_192 0xul
First off, I messed up on the FIFO size defines in mach64_drv.h (drm
kernel module), they should be:
# define MACH64_CMDFIFO_SIZE_MASK 0x0003ul
# define MACH64_CMDFIFO_SIZE_192 0xul
# define MACH64_CMDFIFO_SIZE_128
El Sáb 27 Oct 2001 16:08, Michel Dänzer escribió:
> Hi everybody working on the Mach64 driver,
>
>
> I think it's really important for you to get in touch with the 2D driver
> maintainer, Marc Aurele La France <[EMAIL PROTECTED]>. First because he is
> the single most competent person about the 2D
Hi everybody working on the Mach64 driver,
I think it's really important for you to get in touch with the 2D driver
maintainer, Marc Aurele La France <[EMAIL PROTECTED]>. First because he is
the single most competent person about the 2D driver and probably about
the Mach chips in general, secon
And here goes the proposed patch, for those of you interested. I would like
some feedback about the solutions adopted (for the interlocking and also the
host.def changes) before updating the CVS branch.
El Sáb 27 Oct 2001 12:35, Manuel Teira escribió:
> El Vie 26 Oct 2001 22:11, Leif Delgass e
El Vie 26 Oct 2001 22:11, Leif Delgass escribió:
> Manuel, the hang when switching back from a vt to X with Quake running
> hangs both in fullscreen and windowed mode (other GL apps like gears don't
> exhibit this problem, although there is initially some garbage at the top
> of the screen when re
20 matches
Mail list logo
