On Sun, 27 Jul 2008 23:17:44 +1000, andrew clarke [EMAIL PROTECTED] wrote:
On Sun 2008-07-27 12:52:56 UTC+0200, bsd ([EMAIL PROTECTED]) wrote:
I have just received a new system that's planned to be a large scale DNS
server.
I have asked the guy who has setup the hardware not to install X
I'm kind of new to this, so would appreciate a hand. I just got through
configuring a custom kernel. Both makebuild and installbuild take place
with no problems and the kernel boots just like it's supposed to. But
when I try to bring up X I get this error message
to bring up X I get this error message:
_XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/remdog.net:0
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
These three lines only indaicate that you don't have IPv6
I'm kind of new to this, so would appreciate a hand. I just got through
configuring a custom kernel. Both makebuild and installbuild take place
with no problems and the kernel boots just like it's supposed to. But
when I try to bring up X I get this error message
and the kernel boots just like it's supposed to. But
when I try to bring up X I get this error message:
_XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Maybe you forgot something netowrking related
try to bring up X I get this error message:
_XSERVTransSocketINETCreateListener: ...SocketCreateListener() failed
_XSERVTransMakeAllCOTSServerListeners: server already running
Maybe you forgot something netowrking related. Please show a diff(1) of
you kernel configurations, see
Problem solved. Somehow I didn't just comment out, I actually deleted
this line:
options INET6 # IPv6 communications protocols
Weird. Anyway, I reinserted the line, and now everything works fine.
Rem
___
saw that, but I've got a custom kernel without INET6, and X is running
fine here. I get the same first three lines of the error message in my
Xorg.0.log file
My X server is compiled without hal support. Maybe that makes
the difference.
You could try starting X with 'startx -- -nolisten tcp
the line, and now everything works fine.
I saw that, but I've got a custom kernel without INET6, and X is running
fine here. I get the same first three lines of the error message in my
Xorg.0.log file
My X server is compiled without hal support. Maybe that makes
the difference.
X with HAL
Hello,
since FreeBSD 5.0 I was using 'pf' as the packet filter on FreeBSD due
to some performance advantages over ipfw in the time when FreeBSD was
introduced. Now I'm al littel bit detached from development and status
quo. I read about problems in FreeBSD 7 when using 'pf' in a bridged
Hello
I am trying to run GNUStep applications on my machine.
After installing all the applications and libraries and configuring the
environment I get the following error when for instance I start any
GNUstep app ie. TextEdit, Gorm ...
2008-07-06 20:35:18.082 TextEdit[911] X-Windows error
On Wed, Jul 02, 2008 at 07:13:50PM -0700, Gary Kline wrote:
would this works, say in .zlogin, to say that X is up:
if [ -e /tmp/.X11-unix/X0 ]
then
echo X is up.
exit 0;
else
echo No X yet
exit 1
On Thu, Jul 03, 2008 at 04:36:20PM +0100, Daniel Bye wrote:
On Wed, Jul 02, 2008 at 07:13:50PM -0700, Gary Kline wrote:
would this works, say in .zlogin, to say that X is up:
if [ -e /tmp/.X11-unix/X0 ]
then
echo X is up.
exit 0;
else
would this works, say in .zlogin, to say that X is up:
if [ -e /tmp/.X11-unix/X0 ]
then
echo X is up.
exit 0;
else
echo No X yet
exit 1;
fi
or is there something more clever
I had the same problem when 2 weeks ago i installed FreeBSD7.
the solution was:
# Xorg -configure to create an default xorg.conf file.
{http://www.freebsd.org/doc/en/books/handbook/x-config.html}
Apparently for the mouse to work it needs a default{at least} xorg.conf file.
-nicolas
PS
Just installed FBSD 7, after being gone from FBSD the last 3 years.
During boot I see that the mouse is detected as ums0, but cannot get it
to work in X11. I cannot find any xorg.conf. or xorg.conf.new files. I
have gnome installed and working, so I know X is working properly. Any
suggestions
I know X is working properly. Any
suggestions on the usb mouse?
Thanks.
Using a Logitech MX510 usb mouse in here.
[EMAIL PROTECTED] ~]% cat /etc/X11/xorg.conf
...
Section InputDevice
# generated from default
Identifier Mouse0
Driver mouse
Option Protocol auto
is detected as ums0, but cannot get it
to work in X11. I cannot find any xorg.conf. or xorg.conf.new files. I
have gnome installed and working, so I know X is working properly. Any
suggestions on the usb mouse?
Thanks.
Using a Logitech MX510 usb mouse in here.
[EMAIL PROTECTED] ~]% cat /etc
is detected as ums0, but cannot get it
to work in X11. I cannot find any xorg.conf. or xorg.conf.new files. I
have gnome installed and working, so I know X is working properly. Any
suggestions on the usb mouse?
Thanks.
Using a Logitech MX510 usb mouse in here.
[EMAIL PROTECTED] ~]% cat /etc
I ran update.locatedb, twice, and ran locate xorg.conf and locate
xorg.conf.new. The only result was for xorg.conf found in
/usr/local/man/man5/xorg.conf.5.gz
--
Chip
Gonzalo Nemmi wrote:
No ..
Run a locate xorg.conf to see what xorg.conf file is beign used to run
gnome ..
Check under
know X is working properly. Any
suggestions on the usb mouse?
Thanks.
You do have 'moused' enabled?
Malcolm
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail
file. Then follow the instructions on the screen and run X using the
xorg.conf.new file that it creates to verify that X will work.
If it does, copy the xorg.conf.new file to /etc/xorg.conf and your mouse
should work fine.
Paul Schmehl
If it isn't already obvious,
my opinions are my own
,--- Chip writes:
| Just installed FBSD 7, after being gone from FBSD the last 3
| years. During boot I see that the mouse is detected as ums0, but
| cannot get it to work in X11. I cannot find any xorg.conf. or
| xorg.conf.new files. I have gnome installed and working, so I know X
| is working
, after being gone from FBSD the last 3 years.
During boot I see that the mouse is detected as ums0, but cannot get it
to work in X11. I cannot find any xorg.conf. or xorg.conf.new files. I
have gnome installed and working, so I know X is working properly. Any
suggestions on the usb mouse?
Thanks
Thanks for the tip, did that, and verified that the mouse is set to auto
in the mouse section, still no mouse in any X window manager. Back out
at the terminal I unplugged the mouse and plugged it back in and get
this error -
unable to open /dev/ums0: no such file or directory
but when I view
Chip wrote:
Thanks for the tip, did that, and verified that the mouse is set to
auto in the mouse section, still no mouse in any X window manager.
Back out at the terminal I unplugged the mouse and plugged it back in
and get this error -
unable to open /dev/ums0: no such file or directory
Ok, it's working now, thanks for all the suggestions, you got me
straightened out. Once I got a xorg.conf.new configured correctly I
forgot to copy it to /etc/X11. Dummy me, heheheh. (Been a long time
since my last experience with BSD, about 3 years.)
Thanks guys,
Chip
Gonzalo Nemmi wrote:
--On June 26, 2008 7:52:07 PM -0700 Chip [EMAIL PROTECTED] wrote:
Thanks for the tip, did that, and verified that the mouse is set to auto
in the mouse section, still no mouse in any X window manager. Back out
at the terminal I unplugged the mouse and plugged it back in and get
this error
Paul Schmehl wrote:
What version of FreeBSD are you running?
7.0-Release
If 7.0 STABLE, you should probably csup source and rebuild kernel and
world. I had a similar problem with the early release and it was
related to usb devices not being detected (which sounds like what your
problem
After I had installed FreeBSD-7.0-R and enabled gdm in
/etc/rc.conf, the system freezes when I try to enter gnome interface
through GDM. When I type my blank password, the script fails to go on
___
freebsd-questions@freebsd.org mailing list
On Sat, Jun 07, 2008 at 12:20:46PM -0500, luizbcampos wrote:
After I had installed FreeBSD-7.0-R and enabled gdm in
/etc/rc.conf, the system freezes when I try to enter gnome interface
through GDM. When I type my blank password, the script fails to go on
I believe gdm/kdm/xdm hates
Help, I've googled my fingers off up to the elbow and no luck:o)
Sound works but skips or has gaps at about 1 second intervals.
I'm running a fresh install of FreeBSD 7.0 Release (AMD64.)
/boot/loader.conf contains:
snd_hda_load=YES
You might want to play with some hw.snd sysctls,
Help, I've googled my fingers off up to the elbow and no luck:o)
Sound works but skips or has gaps at about 1 second intervals.
I'm running a fresh install of FreeBSD 7.0 Release (AMD64.)
/boot/loader.conf contains:
snd_hda_load=YES
Other info:
Main board = Asus A8V-X AMD64 w/ on-board sound
:
snd_hda_load=YES
Other info:
Main board = Asus A8V-X AMD64 w/ on-board sound: VIA VT8251/8237A
High Definition Audio Controller
$ cat /dev/sndstat
FreeBSD Audio Driver (newpcm: 64bit 2007061600/amd64)
Installed devices:
pcm0: VIA VT8251/8237A High Definition Audio Controller
at memory
Hello,
I just installed FreeBSD 7.0 on a Dell Vostro 1200. It has Intel's
GM965 chipset and I cannot get X to work at the right resolution of
1280x800.
I updated and reinstalled the x11-drivers/x11-video-i810 and
x11-drivers/x11-intel ports. But X still dies whenever I tell it to
use i810 driver
On Fri, May 16, 2008 at 10:51 PM, Nishita Desai [EMAIL PROTECTED] wrote:
I updated and reinstalled the x11-drivers/x11-video-i810 and
x11-drivers/x11-intel ports.
Sorry, that should be xf86-video-i810 and xf86-video-intel.
Regards,
Nishita
___
Nishita Desai wrote:
On Fri, May 16, 2008 at 10:51 PM, Nishita Desai [EMAIL PROTECTED] wrote:
I updated and reinstalled the x11-drivers/x11-video-i810 and
x11-drivers/x11-intel ports.
Sorry, that should be xf86-video-i810 and xf86-video-intel.
Regards,
Nishita
You only need
Nishita Desai writes:
Nishita Hello,
Nishita I just installed FreeBSD 7.0 on a Dell Vostro 1200. It has Intel's
Nishita GM965 chipset and I cannot get X to work at the right resolution of
Nishita 1280x800.
Nishita I updated and reinstalled the x11-drivers/x11-video-i810
On Fri, May 16, 2008 at 11:04 PM, Dominic Fandrey [EMAIL PROTECTED] wrote:
You only need xf86-video-intel and enter intel as the Driver in your
xorg.conf. I'm running a GM965 at 1440x900 this way.
I even think that x11-video-i810 and xf86-video-intel conflict. So best
deinstall both and only
xorg.conf. I'm running a GM965 at 1440x900 this way.
I even think that x11-video-i810 and xf86-video-intel conflict. So best
deinstall both and only install xf86-video-intel afterwards.
I cannot pkg_delete nor pkg_deinstall xf86-video-i810. Here's the error:
--
pkg_delete: package
Nishita Desai writes:
Nishita On Fri, May 16, 2008 at 11:04 PM, Dominic Fandrey [EMAIL
PROTECTED] wrote:
You only need xf86-video-intel and enter intel as the Driver in your
xorg.conf. I'm running a GM965 at 1440x900 this way.
I even think that x11-video-i810 and
On Fri, May 16, 2008 at 11:27 PM, Wojciech Puchar
[EMAIL PROTECTED] wrote:
deinstall
xorg
xorg-drivers (both are meta-packages)
cd /usr/ports/x11-drivers/xorg-drivers
make config
select drivers you need
then make install clean
Thank you all. That seems to have done it.
reg.,
Nishita
Johan Dowdy wrote:
What do you mean by access?
I mean read, sorry for the unclear question.
A simple way to get the output would be(presuming the 8th column has the
data you want):
iostat -x | awk '{ print $8 }'
This could be redirected to a file or processed ins a shell script etc.
What
Is there a standard way to access, with a scripting language (php, perl,
etc.) the output of -
iostat -x
I am particularly interested in the %b column (HDD utilization).
I am not sure if reading the output and regex-ing the Nth column is the
right approach, or there is a more intelligent one
What do you mean by access?
A simple way to get the output would be(presuming the 8th column has the
data you want):
iostat -x | awk '{ print $8 }'
This could be redirected to a file or processed ins a shell script etc.
What is it that you want to do' with the output?
-J
On 5/13/08 12:22
Hello list,
I have a requirement to automatically mount a USB disk to, say, ~backup/data
automatically when the device is plugged to into the machine.
I can handle/manage the umount part.
--
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254733744121/+254722743223
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _
El día Wednesday, May 07, 2008 a las 01:32:10PM +0300, Odhiambo Washington
escribió:
Hello list,
I have a requirement to automatically mount a USB disk to, say, ~backup/data
automatically when the device is plugged to into the machine.
I can handle/manage the umount part.
You could use
Odhiambo Washington wrote:
Hello list,
I have a requirement to automatically mount a USB disk to, say, ~backup/data
automatically when the device is plugged to into the machine.
I can handle/manage the umount part.
Have a look at:
http://www.freebsd.org/cgi/query-pr.cgi?pr=122726
This port
On Apr 8, 7:35 am, Tsu-Fan Cheng [EMAIL PROTECTED] wrote:
Hi,
I found that I can't start x-window because of some keysym error,
when entering X using xinit, I have these on the screen:
expected keysym, gotXF86KbdLightOnOff: line 70 of pc
[snip]
Do you also have an error about libXft.so.2
I am trying to add performance monitor to a php application working on a
dedicated server and one of the informations I would like to collect is
the hard drives load, which, as far as I could find out, can be seen in
the %b of iostat -x.
What would be the most reliable way to extract
i'm having problems enabling MSI-X for my Ethernet driver on 6.3.
my problem is that pci_msix_count(dev) returns 0, as if my device does not
support MSI-X.
where should I publish my device's MSI-X capabilities?
Yony
___
freebsd-questions@freebsd.org
On Wed, Apr 16, 2008 at 12:27:03PM -0400, Fred Schnittke wrote:
Hi:
I've installed FreeBSD 7.0, just a standard install with X. I load XDM
via /usr/local/etc/rc.d/x.sh, which states:
/usr/local/bin/xset s off
/usr/local/bin/xdm
But I can't get the screensaver to disable. After about
Hi:
I've installed FreeBSD 7.0, just a standard install with X. I load XDM
via /usr/local/etc/rc.d/x.sh, which states:
/usr/local/bin/xset s off
/usr/local/bin/xdm
But I can't get the screensaver to disable. After about 10 minutes of
sitting at the XDM Login Prompt, the screen goes blank.
Can
Hi,
I found that I can't start x-window because of some keysym error,
when entering X using xinit, I have these on the screen:
expected keysym, got XF86KbdLightOnOff: line 70 of pc
expected keysym, got XF86KbdBrightnessDown: line 71 of pc
expected keysym, got XF86KbdBrightnessUp: line 72 of pc
:03:40 +0200
Frank Wißmann [EMAIL PROTECTED] wrote:
Hi all!
Hope there's somebody out there who can help me with the following problem:
When I type startx as root all is coming up as expected, the X-Server
and twm as WM. When I stop it, log in as a normal user and do the same
there is only a grey
Warren Block wrote:
On Thu, 3 Apr 2008, Frank Wi?mann wrote:
Hope there's somebody out there who can help me with the following
problem:
When I type startx as root all is coming up as expected, the
X-Server and twm as WM. When I stop it, log in as a normal user and do
the same there is only
there's somebody out there who can help me with the following
problem:
When I type startx as root all is coming up as expected, the X-Server
and twm as WM. When I stop it, log in as a normal user and do the same
there is only a grey screen with a mouse-cursor coming up and doing
nothing
Frank Wißmann wrote:
Hi all!
Hope there's somebody out there who can help me with the following problem:
When I type startx as root all is coming up as expected, the X-Server
and twm as WM. When I stop it, log in as a normal user and do the same
there is only a grey screen with a mouse-cursor
Hi all!
Hope there's somebody out there who can help me with the following problem:
When I type startx as root all is coming up as expected, the X-Server
and twm as WM. When I stop it, log in as a normal user and do the same
there is only a grey screen with a mouse-cursor coming up and doing
On Thu, Apr 03, 2008 at 09:03:40PM +0200, Frank Wißmann wrote:
Hi all!
Hope there's somebody out there who can help me with the following problem:
When I type startx as root all is coming up as expected, the X-Server and
twm as WM. When I stop it, log in as a normal user and do the same
PROTECTED] wrote:
Hi all!
Hope there's somebody out there who can help me with the following problem:
When I type startx as root all is coming up as expected, the X-Server
and twm as WM. When I stop it, log in as a normal user and do the same
there is only a grey screen with a mouse-cursor
Roland Smith wrote:
On Thu, Apr 03, 2008 at 09:03:40PM +0200, Frank Wißmann wrote:
Hi all!
Hope there's somebody out there who can help me with the following problem:
When I type startx as root all is coming up as expected, the X-Server and
twm as WM. When I stop it, log in as a normal user
, the
X-Server and twm as WM. When I stop it, log in as a normal user and do
the same there is only a grey screen with a mouse-cursor coming up and
doing nothing until I kill the X-Server with Ctrl-Alt-Backspace. On the
original screen from which I tried to start is shown the following error
:
When I type startx as root all is coming up as expected, the X-Server
and twm as WM. When I stop it, log in as a normal user and do the same
there is only a grey screen with a mouse-cursor coming up and doing
nothing until I kill the X-Server with Ctrl-Alt-Backspace. On the
original screen
On Thu, 3 Apr 2008, Frank Wi?mann wrote:
Hope there's somebody out there who can help me with the following problem:
When I type startx as root all is coming up as expected, the X-Server and
twm as WM. When I stop it, log in as a normal user and do the same there is
only a grey screen
On Thu, 3 Apr 2008, herbert langhans wrote:
can you start twm when you log in as a user? It smells like some
permission issue from xfce. You could backup all the xfce files with
the actual permissions and then set them all to 777 and try to start
it.
Don't bring out the hammer until after
and the em driver (freebsd 7.x)
On Mon, Mar 31, 2008 at 02:09:22PM -0800, Ted Mittelstaedt wrote:
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Walker
Sent: Monday, March 31, 2008 11:37 AM
To: Kent Hauser; freebsd-questions@freebsd.org
Subject: Re: Wake
-Original Message-
From: Jerry McAllister [mailto:[EMAIL PROTECTED]
Sent: Monday, March 31, 2008 2:46 PM
To: Ted Mittelstaedt
Cc: Walker; Kent Hauser; freebsd-questions@freebsd.org
Subject: Re: Wake-on-LAN and the em driver (freebsd 7.x)
On Mon, Mar 31, 2008 at 02:09:22PM
-Original Message-
From: Kent Hauser [mailto:[EMAIL PROTECTED]
Sent: Monday, March 31, 2008 3:49 PM
To: Jerry McAllister
Cc: Ted Mittelstaedt; Walker; freebsd-questions@freebsd.org
Subject: Re: Wake-on-LAN and the em driver (freebsd 7.x)
You comments got me to thinking, I have tossed
How can I get the WOL (wake-on-lan) feature to work on my 7-stable system? I
have a dual-boot system with an Intel PRO/1000 PT card that works great with
FreeBSD, but the WOL only works under XP. Is there an ifconfig option (or
similar) to enable WOL under FreeBSD?
I notice that the LED on the
On Mon, Mar 31, 2008 at 6:31 AM, Kent Hauser [EMAIL PROTECTED] wrote:
How can I get the WOL (wake-on-lan) feature to work on my 7-stable system? I
have a dual-boot system with an Intel PRO/1000 PT card that works great with
FreeBSD, but the WOL only works under XP. Is there an ifconfig option
On Mon, Mar 31, 2008 at 5:23 AM, Walker [EMAIL PROTECTED] wrote:
FWIW;
I have two 7.0-RELEASE boxes with single (on board) and dual
(pro/1000) em NICs. WOL works fine on both.
The link light must be on after FreeBSD shuts down for WOL to work.
You might try using the latest proboot.exe
On Mon, 2008-03-31 at 08:43 -1000, Kent Hauser wrote:
On Mon, Mar 31, 2008 at 5:23 AM, Walker [EMAIL PROTECTED] wrote:
FWIW;
I have two 7.0-RELEASE boxes with single (on board) and dual
(pro/1000) em NICs. WOL works fine on both.
The link light must be on after FreeBSD shuts
On Mon, Mar 31, 2008 at 2:43 PM, Kent Hauser [EMAIL PROTECTED] wrote:
Thanks for the pointer. I tried the proboot.exe utilities, but the must run
in a dos environment -- not under an XP command window.
Is there an easier way? I'm not sure how I'm going to get my machine booted
into DOS --
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Kent Hauser
Sent: Monday, March 31, 2008 10:44 AM
To: Walker
Cc: freebsd-questions@freebsd.org
Subject: Re: Wake-on-LAN and the em driver (freebsd 7.x)
On Mon, Mar 31, 2008 at 5:23 AM, Walker [EMAIL
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] Behalf Of Walker
Sent: Monday, March 31, 2008 11:37 AM
To: Kent Hauser; freebsd-questions@freebsd.org
Subject: Re: Wake-on-LAN and the em driver (freebsd 7.x)
I would like to know of any other easier ways
driver (freebsd 7.x)
I would like to know of any other easier ways to do this.
Any network admin worth his salt has an old win98 system tucked
away that can be used to create bootable dos cd's.
Don't know much about the value of salt, but the old Win 98 machine
I have around has
To: Kent Hauser; freebsd-questions@freebsd.org
Subject: Re: Wake-on-LAN and the em driver (freebsd 7.x)
I would like to know of any other easier ways to do this.
Any network admin worth his salt has an old win98 system tucked
away that can be used to create bootable dos cd's.
Don't
/obsolete/linuxthreads/libpthread.so.0 -
libpthread-0.10.so
lrwxr-xr-x 1 root wheel 8 Feb 29 12:21 /usr/lib/libpthread.a - libthr.a
-r--r--r-- 1 root wheel 136020 Feb 29 16:16
/usr/local/lib/compat/libpthread.so.1
-r-xr-xr-x 1 root wheel 43284 Oct 17 00:52
/usr/local/lib/valgrind
Feb 29 13:57
/usr/compat/linux/lib/libpthread.so.0 - libpthread-2.3.6.so
lrwxrwxrwx 1 root wheel 18 Feb 29 13:57
/usr/compat/linux/lib/obsolete/linuxthreads/libpthread.so.0 -
libpthread-0.10.so
lrwxr-xr-x 1 root wheel 8 Feb 29 12:21 /usr/lib/libpthread.a -
libthr.a
-r--r
/obsolete/linuxthreads/libpthread.so.0 -
libpthread-0.10.so
lrwxr-xr-x 1 root wheel 8 Feb 29 12:21 /usr/lib/libpthread.a - libthr.a
-r--r--r-- 1 root wheel 136020 Feb 29 16:16
/usr/local/lib/compat/libpthread.so.1
-r-xr-xr-x 1 root wheel 43284 Oct 17 00:52
/usr/local/lib/valgrind
Feb 29 13:57
/usr/compat/linux/lib/libpthread.so.0 - libpthread-2.3.6.so
lrwxrwxrwx 1 root wheel 18 Feb 29 13:57
/usr/compat/linux/lib/obsolete/linuxthreads/libpthread.so.0 -
libpthread-0.10.so
lrwxr-xr-x 1 root wheel 8 Feb 29 12:21 /usr/lib/libpthread.a -
libthr.a
-r--r--r
Dmitry RCL Rekman wrote:
Hi,
On Sat, Mar 22, 2008 at 3:52 PM, Kris Kennaway [EMAIL PROTECTED] wrote:
RCL wrote:
Hi,
I'm having the same troubles as Leslie Jensen when compiling KDE (or
anything that uses uic, e.g. amarok):
compile process stucks with the following message:
Mutex unlock
. kdebase3 (when
uic is used).
Actually, the problem was tracked down to be inside uic. When built on my
(and Leslie's) 7.0 upgraded from 6.x system, uic does not link to
libthr.so, while in a newly-installed 7.0 it does.
So one of people here (Mel) asked to provide the actual commandline used
. kdebase3 (when
uic is used).
Actually, the problem was tracked down to be inside uic. When built on my
(and Leslie's) 7.0 upgraded from 6.x system, uic does not link to
libthr.so, while in a newly-installed 7.0 it does.
It should not be linking (directly) to libthr at all, it should be
linking
Hi,
On Sat, Mar 22, 2008 at 6:14 PM, Kris Kennaway [EMAIL PROTECTED] wrote:
Actually, the problem was tracked down to be inside uic. When built on
my
(and Leslie's) 7.0 upgraded from 6.x system, uic does not link to
libthr.so, while in a newly-installed 7.0 it does.
It should
Dmitry RCL Rekman wrote:
Hi,
On Sat, Mar 22, 2008 at 6:14 PM, Kris Kennaway [EMAIL PROTECTED]
mailto:[EMAIL PROTECTED] wrote:
Actually, the problem was tracked down to be inside uic. When
built on my
(and Leslie's) 7.0 upgraded from 6.x system, uic does not link
this failing is if your /lib is not
correctly populated. What is the output of
ls -l /lib/libthr* /usr/lib/libpthr*
# ls -l /lib/libthr* /usr/lib/libpthr*
-r--r--r-- 1 root wheel 66928 Feb 29 12:20 /lib/libthr.so.3
lrwxr-xr-x 1 root wheel 8 Feb 29 12:21 /usr/lib/libpthread.a -
libthr.a
lrwxr-xr-x 1 root wheel 8 Feb 29 12:21 /usr/lib/libpthread.a -
libthr.a
lrwxr-xr-x 1 root wheel 10 Feb 29 12:21 /usr/lib/libpthread_p.a -
libthr_p.a
Yep, your world is broken, you are missing a /usr/lib/libpthread.so symlink.
Kris
*
# ls -l /lib/libthr* /usr/lib/libpthr*
-r--r--r-- 1 root wheel 66928 Feb 29 12:20 /lib/libthr.so.3
lrwxr-xr-x 1 root wheel 8 Feb 29 12:21 /usr/lib/libpthread.a -
libthr.a
lrwxr-xr-x 1 root wheel 10 Feb 29 12:21 /usr/lib/libpthread_p.a -
libthr_p.a
Yep, your world
lrwxr-xr-x 1 root wheel 8 Feb 29 12:21
/usr/lib/libpthread.a -
libthr.a
lrwxr-xr-x 1 root wheel 10 Feb 29 12:21
/usr/lib/libpthread_p.a -
libthr_p.a
Yep, your world is broken, you are missing a /usr/lib/libpthread.so
symlink.
Ok, I created
*
# ls -l /lib/libthr* /usr/lib/libpthr*
-r--r--r-- 1 root wheel 66928 Feb 29 12:20 /lib/libthr.so.3
lrwxr-xr-x 1 root wheel 8 Feb 29 12:21
/usr/lib/libpthread.a -
libthr.a
lrwxr-xr-x 1 root wheel 10 Feb 29 12:21
/usr/lib
Hi,
I have a freebsd 7.0 release with xorg 7.3 installed on a i386 with a
NVIDIA GeForce Go 7300
Official nvidia drivers installed and apparently no problems.
In the xorg.0.log file there aren't any errors, glx is correctly loaded
etc..
My system starts without X and then I use startx to start X
is correctly loaded etc..
My system starts without X and then I use startx to start X server and
KDE3.5 (if I'm not wrong about the version).
Some errors are written on the console and I'm not able to see them!
To see them I have to stop X (with ctrl+ bkspc) and use scroll lock to
see what's
starts without X and then I use startx to start X server and
KDE3.5 (if I'm not wrong about the version).
Some errors are written on the console and I'm not able to see them!
To see them I have to stop X (with ctrl+ bkspc) and use scroll lock to
see what's there.
I found the console full of X error: bad
in /etc/hosts??
Then I get lots of line(130!) like :
kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop'
specifies undefined mimetype/servicetype 'application/x-tbz2'
kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop'
specifies undefined mimetype
undefined mimetype/servicetype 'application/x-tbz2'
kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop'
specifies undefined mimetype/servicetype 'application/zip'
kbuildsycoca: WARNING: '/usr/local/share/applications/kde/ark.desktop'
specifies undefined mimetype/servicetype
Is it something wrong in /etc/hosts??
It could be your /etc/hosts or /etc/hosts.allow or you may need to add:
-listen_tcp
to your startx commandline.
I supposed the problem was there! I'll look at -listen_tcp and at hosts.allow.
I have doubts about setting hosts. X used to give me errors about
This error refers to the artsd daemon already running, or the system thinks
this daemon is running. You should open a terminal window and do:
ps -ax|grep -i art
and see if the artsd daemon is running or not. If it is not, you may need to
force it to start.
I'll try that later!
If I do ps
At 01:07 PM 3/21/2008, Luca Presotto wrote:
This error refers to the artsd daemon already running, or the system
thinks this daemon is running. You should open a terminal window and do:
ps -ax|grep -i art
and see if the artsd daemon is running or not. If it is not, you may
need to force it
901 - 1000 of 3901 matches
Mail list logo
