On Dec 02, Jamie Bowden wrote:
I have a new machine that I've just installed 5.1-R on, and cvsup'd to -C.
I'm attempting to build X, and am getting a core dump from rman during the
process.
I had this happen too. I did something really hack-ish to get around it
(like delete that
hack-ish to get around
it (like delete that documentation or some other unspeakable hack.)
The coredump is due to bugs in the rman command (which is installed by
the imake port, believe it or not). I submitted a bugreport on it in
July, and hopefully it will be in Xfree86 4.4.0. Installing
it will be in Xfree86 4.4.0. Installing the
textproc/rman port may mask the bug until then, or you can drop this
file into ports/devel/imake-4/files and rebuild imake.
Installing /usr/ports/emulators/linux_compat seems to fix this. I have no
idea why, but I went ahead and installed it so I
Hi...
after updating my 5.1-current machine:
a) new kernel
b) new world
c) all packages (including XFree86)
d) newest gnome-packages (using marcusmerge)
i got these msgs in XFree86.0.log
Warning: font renderer for .pcf already registered at priority 0
Warning
On Friday 24 October 2003 02:00, James Tanis wrote:
From the log file:
(II) Primary Device is:
(--) Assigning device section with no busID to primary device
(WW) RADEON: No matching Device section for instance (BusID
PCI:1:0:1) found (EE) No devices detected.
I did not attempt
At Thu, 23 Oct 2003 20:00:38 -0400,
James Tanis wrote:
Attempted this, first did a deinstall of XFree86-Server and then
built/installed XFree86-Server-snap. It built and installed perfectly fine,
from what I can see it runs fine too.. but I get the same error. You
weren't wrong
On Fri, 2003-10-24 at 00:13, Thomas Schwarzkopf wrote:
On Friday 24 October 2003 02:00, James Tanis wrote:
From the log file:
(II) Primary Device is:
(--) Assigning device section with no busID to primary device
(WW) RADEON: No matching Device section for instance (BusID
PCI:1:0:1)
I'm having problems with XFree86 that result from the fact that
the ATI Radeon 9800 is not supported by the current 4.3.0 radeon driver. I
would like to upgrade to current/cvs version of XFree86, 4.3.99 since the
next release isn't going to be for around another 2 months. My question
On Thu, 2003-10-23 at 13:59, James Tanis wrote:
I'm having problems with XFree86 that result from the fact that
the ATI Radeon 9800 is not supported by the current 4.3.0 radeon driver. I
would like to upgrade to current/cvs version of XFree86, 4.3.99 since the
next release isn't
Attempted this, first did a deinstall of XFree86-Server and then
built/installed XFree86-Server-snap. It built and installed perfectly fine,
from what I can see it runs fine too.. but I get the same error. You
weren't wrong, in the log once of the supported cards listed is the ATI
On Thu, 2003-10-23 at 17:00, James Tanis wrote:
Attempted this, first did a deinstall of XFree86-Server and then
built/installed XFree86-Server-snap. It built and installed perfectly fine,
from what I can see it runs fine too.. but I get the same error. You
weren't wrong
Hi, I'm running 5.1-CURRENT (sources/ports from Oct/13) and
the X package isn't compiling:
FeaNoR# make package
=== Installing for XFree86-4.3.0,1
=== XFree86-4.3.0,1 depends on executable: xvinfo - not found
===Verifying package for xvinfo in /usr/ports/x11/XFree86-4-clients
On Tue, 2003-10-14 at 17:21, Rossam Souza Silva wrote:
Hi, I'm running 5.1-CURRENT (sources/ports from Oct/13) and
the X package isn't compiling:
FeaNoR# make package
=== Installing for XFree86-4.3.0,1
=== XFree86-4.3.0,1 depends on executable: xvinfo - not found
===Verifying
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying:
make: don't know how to make
/usr/ports/x11/XFree86-4-clients/work/xc/exports/lib/libfntstubs.a. Stop
David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying:
make: don't know how to make /usr/ports/x11/XFree86-4-clients/work/xc/exports
On Mon, Oct 13, 2003 at 03:51:06PM -0700, Peter Wemm wrote:
David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying:
make: don't
On Mon, 2003-10-13 at 15:51, Peter Wemm wrote:
David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying:
make: don't know how
Eric Anholt wrote:
On Mon, 2003-10-13 at 15:51, Peter Wemm wrote:
David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying
On Mon, 2003-10-13 at 16:05, Peter Wemm wrote:
Eric Anholt wrote:
On Mon, 2003-10-13 at 15:51, Peter Wemm wrote:
David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds
Peter == Peter Wemm [EMAIL PROTECTED] writes:
Peter David Gilbert wrote:
I don't really have a clue where to look for this fix as there
seems to be a serious amount of magic going into the divided
XFree86-4 port builds, but my XFree86-4-clients port fails saying:
make: don't know how
Peter == Peter Wemm [EMAIL PROTECTED] writes:
Peter Eric Anholt wrote:
On Mon, 2003-10-13 at 15:51, Peter Wemm wrote: David Gilbert
wrote: I don't really have a clue where to look for this fix as
there seems to be a serious amount of magic going into the
divided XFree86-4 port builds
On Mon, 2003-10-13 at 14:54, David Gilbert wrote:
I don't really have a clue where to look for this fix as there seems
to be a serious amount of magic going into the divided XFree86-4 port
builds, but my XFree86-4-clients port fails saying:
make: don't know how to make
/usr/ports/x11
On a recent -current
FreeBSD bishop.uberduper.com 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Mon Oct 6
15:12:45 PDT 2003
I am unable to build XFree86-4-clients from ports. Here's the last little bits
from the build.
macro in not recognized -- ignoring
making all in programs/bdftopcf...
cc -O -pipe
On Tue, Oct 07, 2003 at 12:06:31PM -0700, James Satterfield wrote:
On a recent -current
FreeBSD bishop.uberduper.com 5.1-CURRENT FreeBSD 5.1-CURRENT #0: Mon Oct 6
15:12:45 PDT 2003
I am unable to build XFree86-4-clients from ports. Here's the last little bits
from the build.
macro
While doing a portupgrade on my 5.0R-5.1-CURRENT migrated
system I just saw the following message pass by on my screen:
XFree86-libs-4.0.3-5.i386.rpm
/sbin/ldconfig: File /usr/lib/libGL.so.1.0.4365 is too small, not checked.
/sbin/ldconfig: File /usr/lib/libGL.so.1 is too small, not checked
I have an HP Compaq Presario X1000 (Model X1018CL) with an ATI Mobility
Radeon 9200 (M9 / RV250?) and a 15.4 widescreen WSXGA+ capable of
1280x800. I installed XFree86 4.3.0 on FreeBSD 5.1 and it seems like the
only odd message I'm getting before aborting the startx is a warning about
a bad
Not to undermine what you guys said, but this is unrelated to the
original post I think. The problem I was having related to acpi, which
Shizuka pointed out. I'm not trying to play nanny here, just don't want
people to get confused =)
On Sun, 2003-08-10 at 21:16, Daniel Flickinger wrote:
On Sun, 10 Aug 2003, Daniel Flickinger wrote:
I had the same problem starting about a year ago when I
finally gave up and upgraded to X4. The problem appears
to be that the X4 driver does not disable the console
mouse and the two of them fight over the interrupts.
Well yeah
motherboard and am having some trouble using
the PS/2 mouse driver under XFree86. I have the protocol set to auto,
and the device set to /dev/psm0. This configuration has worked with
this same Intellimouse in the past. The symptoms are that that when the
mouse is moved, the cursor is only
Hello,
I have an Abit KT266 based motherboard and am having some trouble using
the PS/2 mouse driver under XFree86. I have the protocol set to auto,
and the device set to /dev/psm0. This configuration has worked with
this same Intellimouse in the past. The symptoms are that that when
/2 mouse driver under XFree86. I have the protocol set to auto,
and the device set to /dev/psm0. This configuration has worked with
this same Intellimouse in the past. The symptoms are that that when the
mouse is moved, the cursor is only updated about once a second. After
--- Mike Bohan [EMAIL PROTECTED] wrote:
Hello,
I have an Abit KT266 based motherboard and am having some trouble using
the PS/2 mouse driver under XFree86. I have the protocol set to auto,
and the device set to /dev/psm0. This configuration has worked with
this same Intellimouse
again!
-Mike Bohan
On Sun, 2003-08-10 at 04:02, Shizuka Kudo wrote:
--- Mike Bohan [EMAIL PROTECTED] wrote:
Hello,
I have an Abit KT266 based motherboard and am having some trouble using
the PS/2 mouse driver under XFree86
of the XFree86-libraries
port. So apprently it has been installed? But maybe was removed
by something else? I certainly did not remove these files.
I could solve the problem easily by copying the files back into
place, and I cannot rule out, that the files have been lost
due to my fault. If any of the XFree
fixed, which could explain why it is no longer present on your
system.
This kind of trespassing by packages is difficult to recover from
automatically (i.e. there's no way to indicate that the usual
dependency ordering should be violated and XFree86-libraries should be
reinstalled *after* open
of the
ports fresh, including XFree86.
Now I have XFree86-Server-4.3.0_8 installed.
If I start up X, I cannot put in any key. The mouse works
fine, though. I have to remote log into the box and kill
xdm to get rid of the problem.
The keyboard works perfectly on the console.
I searched the mailing
I have the X server up and running on my machine at work, I'm currently
using it in a desktop configuration (although not my primary desktop yet
because I still need to have a place to finish off some kernel
optimizations).
The first patch is against ports/x11/XFree86-4-libraries:
http
Hi guys,
Attached is a gdb trace of a panic on a -current system from a few
days ago. It seems like it was caused by a select(2) in XFree86.
Although I was testing some unrelated changes in libthr kernel code,
I have seen this panic before (about 2 weeks ago) on a stock
kernel.
FreeBSD
/glut_examples/examples/cube.c
The hardware is:
AMD Athlon XP 1800+, MSI KT4V (KT400/VT8235), 256MB DDR333 PC2700,
Matrox G450 32MB AGP4X
The system runs -CURRENT (last updated 2 days ago).
Some of the XFree86 ports installed (and their versions):
XFree86-4.3.0,1, XFree86-Server-4.3.0_8
Hello,
Thanks for the advices of the mailing group. I finally figure out the
problem of my previous mail concerning the X under XFree86 4.3.0 with
Freebsd-5.1 beta 2. I use the same VGA card with the crt mon and everything
work ok without extra work for the X-config file. The problem may
- Original Message -
From: nobody nobody [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, June 03, 2003 1:01 AM
Subject: Radeon VE 7000 VGA card support under xfree86 4.3.0
Hello,
Thanks for the advices of the mailing group. I finally figure out
I tried to build XFree86 from ports since somehow I had no X11
on my server machine - maybe I initially installed a system w/o X11.
Now I want to install X and thought I just install /usr/ports/x11/XFree86.
But compilation failed somewhere in wrapper.c, security/pam_misc.h not found.
I
that it references a Geforce256 -- ignore that,
it only refers to an older NVIDIA card I had, I just didn't change it); it
works for me...:
# File generated by xf86config.
#
# Copyright (c) 1999 by The XFree86 Project, Inc.
#
# Permission is hereby granted, free of charge, to any person obtaining a
# copy
upgrading my XF86 to 4.3.0 over
the weekend.
XFt is a prerequisite for a bunch of stuff, so it was installed on
my machine along with XFree86-4.2.0. However, XFree86-4.2.0 had
already installed its own version of libXft and the include files,
so the Xft port installed on top of the XFree86-4.2.0
Hello,
I've been able to portupgrade my XFree86-4.2.1 system[1] to 4.3.0 expect the
4.3.0 clients port. I've tried completely removing and building it manuly
thru make install but I get the same.
The log from the build can be found here:
http://www4.tpg.com.au/users/jhogge/log
But here
On Sat, 2003-03-22 at 20:38, Alastair G. Hogge wrote:
I've been able to portupgrade my XFree86-4.2.1 system[1] to 4.3.0 expect the
4.3.0 clients port. I've tried completely removing and building it manuly
thru make install but I get the same.
-DMITSHM -DXFT -DXRENDER -c do_text.c
do_text.c
On Saturday, 22 March 2003 22:17, Daniel O'Connor wrote:
On Sat, 2003-03-22 at 20:38, Alastair G. Hogge wrote:
I've been able to portupgrade my XFree86-4.2.1 system[1] to 4.3.0 expect
the 4.3.0 clients port. I've tried completely removing and building it
manuly thru make install but I get
Well it was Xft.
I feel stupid, sorry for wasting peoples time.
Anyways I think I recall what happened, during the portupgrade I was playing
around with X and caused a system crash. This may have happened during the
Xft removal/upgrade stage of portupgrade.
All is well now, thanks Daniel
To
[moving to -ports, I'm not sure it's a -current issue]
Alastair G. Hogge wrote:
On Saturday, 22 March 2003 22:17, Daniel O'Connor wrote:
On Sat, 2003-03-22 at 20:38, Alastair G. Hogge wrote:
I've been able to portupgrade my XFree86-4.2.1 system[1] to 4.3.0 expect
the 4.3.0 clients port
Is it only with me?
XFree86-4-Server cannot be compiled on recent -current,
FreeBSD 5.0-CURRENT #34: Sat Mar 22 13:21:34 JST 2003,
with the following error (patch cannot be applied);
=== Applying FreeBSD patches for XFree86-Server-4.3.0_2
1 out of 2 hunks failed--saving rejects to lib
On Sun, Mar 23, 2003 at 11:57:18AM +0900, Yamada Ken Takeshi wrote:
Is it only with me?
XFree86-4-Server cannot be compiled on recent -current,
FreeBSD 5.0-CURRENT #34: Sat Mar 22 13:21:34 JST 2003,
with the following error (patch cannot be applied);
I think it's you :) That patch
Thank you.
I find that I haven't cvsup x11/XFree86-4-libraries for a while.
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Since upgrading to the latest version of XFree86 available on current
(using portupgrade -r), I cannot login as any users using GDM. I can
login as root...
After doing a few things, I have the following:
login as user
enter password
Your session lasted less than 10 seconds. If you didn't log
One more thing...I am running gdm as such from my /etc/ttys file:
ttyv8 /usr/X11R6/bin/gdm -nodaemon xterm on secure
Anthony Carter
On Thu, 2003-03-20 at 09:23, CARTER Anthony wrote:
Since upgrading to the latest version of XFree86 available on current
(using portupgrade -r), I cannot
): WARNING **: Unable to load panel stock icon 'go'
Extra content at the end of the document
I have already portupgrade -f gnome-panel...
Anthony Carter
On Thu, 2003-03-20 at 09:53, Anthony Carter wrote:
From: CARTER Anthony [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: HELP GDM XFree86
is for, but if I type pkg_delete wrappe-1.0_2 at
the command line, I get:
pkg_delete: package 'wrapper-1.0_2' is required by these other packages
and may not be deinstalled:
XFree86-4.3.0,1
I never installed wrapper, but when I did a portupgrade to the latest
XFree, I guess it installed wrapper
On 20-Mar-2003 CARTER Anthony wrote:
One more thing...I am running gdm as such from my /etc/ttys file:
ttyv8 /usr/X11R6/bin/gdm -nodaemon xterm on secure
I think the GDM documentation says, that you should start it via the supplied
rc.d autostart script in order to avoid certain
It depends on GNOME version... GNOME-1.4.something installs gdm that is
started by init... GNOME-2.2.0 installs gdm that is supposed to start via
/usr/X11R6/etc/rc.d/gdm.sh...
Sincerely, Maxim M. Kazachek
mailto:[EMAIL PROTECTED]
mailto:[EMAIL PROTECTED]
On Thu, 20 Mar 2003
]
Subject: HELP GDM XFree86
Date: 20 Mar 2003 09:23:02 +0100
Since upgrading to the latest version of XFree86 available on current
(using portupgrade -r), I cannot login as any users using GDM. I can
login as root...
After doing a few things, I have the following:
login
Hi,
I updated XFree86 this morning after a cvsup using portupgrade -r...did
all packages for XFree86 (Server, libraries etc. etc.)
I now have a problem with GDM...
I can log in as root using the GDM, but if I log in as another user, it
pops a message up about my session not lasting longer than
CARTER Anthony wrote:
Hi,
I updated XFree86 this morning after a cvsup using portupgrade -r...did
all packages for XFree86 (Server, libraries etc. etc.)
I now have a problem with GDM...
I can log in as root using the GDM, but if I log in as another user, it
pops a message up about my session
Well, the .xsession is executable...
adding my user to the gdm group didn't help...
SUID...New to this...can you explain a little about this...?
XFree86 is dependent on wrapper...it won't uninstall...I can force
it...but...
Anthony
On Wed, 2003-03-19 at 14:43, walt wrote:
CARTER Anthony
Xfree requires wrapper but seems to break GDM for user logins. Is this
normal, and can I force un-install wrapper without breaking anything?
Anthony
XFreeOn Wed, 2003-03-19 at 14:43, walt wrote:
CARTER Anthony wrote:
Hi,
I updated XFree86 this morning after a cvsup using portupgrade -r
wrapper is needed to run script startx by ordinary user, not root... Seems
like gdm works well for me without wrapper.
Shall we need to make XFree86-4.3.0,1 an option to install without wrapper
package?
Sincerely, Maxim M. Kazachek
mailto:[EMAIL PROTECTED]
mailto:[EMAIL
to this:
/usr/X11R6/bin/X@ - XFree86
This *will* break 'startx' for ordinary users. 'Wrapper' is intended
to replace xdm and friends to create the .Xauthority in your home
directory.
If xdm/gdm/kdm don't create the .Xauthority file then something else
must do it -- that something else is 'wrapper'.
You
I realise what wrapper is for, but if I type pkg_delete wrappe-1.0_2 at
the command line, I get:
pkg_delete: package 'wrapper-1.0_2' is required by these other packages
and may not be deinstalled:
XFree86-4.3.0,1
I never installed wrapper, but when I did a portupgrade to the latest
XFree, I
Andrei Popov [EMAIL PROTECTED] writes:
There's something fishy with Xkb in 4.3: whenever I try cyrillic
layouts (e.g. ru, bg, ua, etc.), I cannot type a thing (and yes,
cyrillic fonts are listed in font path).
Running xev shows that event is there. Anyone seen the same
behavior/knows what
Please try setting the locale:
export LC_CTYPE=ru_RU.KOI8-R
or
setenv LC_CTYPE ru_RU.KOI8-R
Yow! Worked -- which is a bit strange: with 4.2 nothing like this was
necessary...
--
Alexander Pohoyda
[EMAIL PROTECTED]
Thanks,
-- Andrei
__
There's something fishy with Xkb in 4.3: whenever I try cyrillic
layouts (e.g. ru, bg, ua, etc.), I cannot type a thing (and yes,
cyrillic fonts are listed in font path). Once I change it to any
latin-based (us, pl, sk, cz, fr, etc.) -- all is ok.
Running xev shows that event is there. Anyone
Am I the only person having problems with a laptop with
Current and XFree86?
I have a Compaq Evo N800c witch runs with 4.7-STABLE and
XFree86 with no problems. The exact same configuration for
X and same version of XFree86-libs etc does not run on
Current a few days old. The problems started
On Mon, Feb 10, 2003 at 11:20:24AM +0100, Gunnar Flygt wrote:
Since it works with 4.7-STABLE it must(?) be a current problem
more than a XFree86 problem. Or?
Any suggestions?
--
Gunnar Flygt, SR
Could you paste your /var/log/XFree86*.log with the error parts? Maybe some will be
able
Resending due to the fact that I didn' include the
/var/log/XFree86.0.log
I have a Compaq Evo N800c witch runs with 4.7-STABLE and
XFree86 with no problems. The exact same configuration for
X and same version of XFree86-libs etc does not run on
Current a few days old. The problems started a few
Since it works with 4.7-STABLE it must(?) be a current problem
more than a XFree86 problem. Or?
I had the same problem -- something to do with files left
over from the original 4.7 installation. Cured by
deinstalling XFree86-* ports, renaming /usr/X11R6 to
something else (in case something
thanks all, securelevel was 2
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
@. Please let me know what
info you'd like to carry on debugging this.
Regards
--Rob
-- Forwarded message --
Date: Tue, 21 Jan 2003 16:05:34 +0200 (SAST)
From: fingers [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: first snag with 5.0 - XFree86 4
howdie
built X 4
with 5.0 - XFree86 4
howdie
built X 4 from source or using package I'm getting:
snip
XFree86 Version 4.2.1 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 3 September 2002
If the server is older than 6-12 months, or if your card is
newer than
: fingers [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: first snag with 5.0 - XFree86 4
howdie
built X 4 from source or using package I'm getting:
snip
XFree86 Version 4.2.1 / X Window System
(protocol Version 11, revision 0, vendor release 6600)
Release Date: 3 September 2002
it happens or goes away after 5.0-RELEASE and/or go back to 4.7.
Or are XFree86-on-FreeBSD problems better dealt with in XFree86 forums?
Thanks.
--
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body of the message
Hello,
Has anyone had any success with this combo?
It compiles fine, but the X server aborts due to bus error (SIGBUS)
generated by something in xf86GetPciBridgeInfo()
(xc/programs/Xserver/hw/xfree86/common/xf86pciBus.c)
Running -CURRENT (World/kernel) as of December 29. XFree86 sources
since at least X version 4.2.0.
Unfortunately, there seems to be no easy fix for the problem, apart from
buying a new video card.
It compiles fine, but the X server aborts due to bus error (SIGBUS)
generated by something in xf86GetPciBridgeInfo()
(xc/programs/Xserver/hw/xfree86/common
On Tue, 2002-12-31 at 11:30, Szilveszter Adam wrote:
Hmmm. I have the same version of X as you (roughly, the tag was already
in place by the time I built although I always use HEAD, I built on 23rd
December) and FreeBSD is from 25th December.
I just updated the sources to HEAD, and I see
when
4.3.0 comes out. (Although I still have gripes with the way the
XFree86-4 metaport works right now: it is very inefficient)
Wish you good luck.
--
Regards:
Szilveszter ADAM
Szombathely Hungary
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe freebsd-current in the body
XFree86 exits on signal 11 immediately after starting on FreeBSD 4.6 and
4.7. It is not possible to run the graphical configuration utility at all.
After running curses configuration utility, running startx produces signal
11. No other debugging information is available. No other messages from
On Tue, Oct 29, 2002 at 10:01:07PM -0800, Paul A. Scott wrote:
XFree86 exits on signal 11 immediately after starting on FreeBSD 4.6 and
4.7. It is not possible to run the graphical configuration utility at all.
After running curses configuration utility, running startx produces signal
11
On Tue, 15 Oct 2002 11:39:22 -0700 (PDT)
Saurabh Gupta [EMAIL PROTECTED] wrote:
Any help will be very much appreciated.
When it freezes again, wait some minutes (~10). If it unfreezes then, it
is a known problem. And if you see some aborts (signal 6) of XFree86,
then it is a known problem too
Hi,
I am running a current from 22nd of september.
I compiled gnome2 using the ports method. after some
help from people in this list i finally installed it.
Now as soon as I startup gnome in X the computer freezes.
So I compiled and installed kde3 and the same thing
happens.
Simple X with just
. (Some of those graphical modules
use beziers.)
My XFree86 crashes pretty much every time I turn my back on my PC for
a few minutes and let xscreensaver kick in.
I don't have a fancy screensaver (blank screen + DPMS), and it even
crashes when I do nothing... I've played some mp3s in a xterm
only. (Some of those graphical modules use
beziers.)
My XFree86 crashes pretty much every time I turn my back on my PC for
a few minutes and let xscreensaver kick in.
Kris
msg43992/pgp0.pgp
Description: PGP signature
helps - or just
set it to blank screen only. (Some of those graphical modules use
beziers.)
My XFree86 crashes pretty much every time I turn my back on my PC for
a few minutes and let xscreensaver kick in.
I don't use screensaver -- my belief is, that the power switch is the
best form
On Sun, Sep 29, 2002 at 12:17:54PM -0700, Eric Anholt wrote:
On Sun, 2002-09-29 at 10:25, Wesley Morgan wrote:
Does this bug effect -stable? It only showed up in -current recently.
Isn't it a bigger chance that something on the FreeBSD side made this bug
much more visible?
On Sun, 29
this won't get fixed until XFree86 4.3.0, but the bug seems
to be in the Type1 font handler only. (a call to abort())
I have removed it from my XFree86 config now, and I'm hoping for no more
Bezier crashes :)
Mvh,
Frode Nordahl
To Unsubscribe: send mail to [EMAIL PROTECTED]
with unsubscribe
:
[snip]
I wonder if it could find the very annoying crashes in the X server.
--
I'm sick of hearing about how big my Beziers are!
I found this on the Xpert mailinglist:
http://www.xfree86.org/pipermail/xpert/2002-June/018300.html
Seems like this won't get fixed until XFree86 4.3.0
.
--
I'm sick of hearing about how big my Beziers are!
I found this on the Xpert mailinglist:
http://www.xfree86.org/pipermail/xpert/2002-June/018300.html
Seems like this won't get fixed until XFree86 4.3.0, but the bug seems
to be in the Type1 font handler only. (a call to abort
On Sun, 2002-09-29 at 10:25, Wesley Morgan wrote:
Does this bug effect -stable? It only showed up in -current recently.
Isn't it a bigger chance that something on the FreeBSD side made this bug
much more visible?
On Sun, 29 Sep 2002, Maxim Sobolev wrote:
I think it should be fixed in
that was a mozilla bug that was supposed to
be fixed.
It seems like the bug has been present in XFree86 all the time. But
some thing has changed in CURRENT that tickles this bug.
I started to experience this after I removed all ports and recompiled
XFree86 with the new GCC 3.2.1.
X also dies
that was supposed to
be fixed.
It seems like the bug has been present in XFree86 all the time. But
some thing has changed in CURRENT that tickles this bug.
I started to experience this after I removed all ports and recompiled
XFree86 with the new GCC 3.2.1.
X also dies with signal 11 some
Wesley Morgan wrote:
Yes, i don't see any -stable systems bombing out. But it _always_ occurrs
when typing. No matter what app...
I've seen in most often when starting X/gnome. Almost always happens
when gnome-panel is just appearing on screen. No typing going on yet,
naturally.
If
in /etc/make.conf you'll get the build failure in
XFree86-4-Server because bsd.cpu.mk will set excplicit -march, not
-mcpu. But the build error happens _only_ if one sets CPUTYPE=p[234]
and not in case CPUTYPE=i686, the latter sets -march=pentiumpro, not
-march=pentium[234]. Hope this is all clear now
I have built XFree86 at least 3 times in the past week, all with varying
levels of optimization, from -O to -O3 and ALWAYS with -march=pentium3.
All of the builds succeeded, although I had stability problems with -O2
and above. Are you _certain_ this is a compiler bug?
On Tue, 24 Sep 2002
On Tue, Sep 24, 2002 at 09:47:44AM -0400, Wesley Morgan [EMAIL PROTECTED] wrote:
I have built XFree86 at least 3 times in the past week, all with varying
levels of optimization, from -O to -O3 and ALWAYS with -march=pentium3.
All of the builds succeeded, although I had stability problems
1 - 100 of 457 matches
Mail list logo
