libaprutil-1.so.4 not found, required by libserf-1.so.0
[Error 19:57:22] Subversion update failed.
[Error 19:57:22] Failed to update the 'freebsd_texlive' ports tree.
Yeah -- you need to update or install the package that provides
libaprutil-1.so. If you're using pkg(8) against a package
On Thu, Sep 12, 2013 at 12:36 AM, Matthew Seaman
m.sea...@infracaninophile.co.uk wrote:
On 11/09/2013 21:03, Antonio Olivares wrote:
[Info 19:57:22] Updating 'freebsd_texlive' source ports tree with method
'svn'.
Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0
[Error
After installing (and reinstalling) devel/lprof,
I keep getting the error:
The QAssistantClient executable was not found. Make sure that
assistant(.exe)is located either in your PATH or in the $QTDIR/bin directory.
Help will not be availble until this is corrected.
I have both
devel
Dear folks,
I am having problems with subject line. I have to fix error by
reinstalling subversion, but it keeps coming back with this error
message.
Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0
=== Returning to list of ports depending on subversion-1.8.3
On 11/09/2013 21:03, Antonio Olivares wrote:
[Info 19:57:22] Updating 'freebsd_texlive' source ports tree with method
'svn'.
Shared object libaprutil-1.so.4 not found, required by libserf-1.so.0
[Error 19:57:22] Subversion update failed.
[Error 19:57:22] Failed to update
encountered several instances where although a required
port is already installed, a dependent port build will claim that
the required library isn't found, and attempt a (re-)install of
that port.
In this example, jbig2dec claims that shared library libpng15.so
is not found, although 'ls' says
test.cc:2:10: fatal error: 'future' file not found
#include future
^
1 error generated.
I guess clang is re-using system headers which belong to older gcc 4.2
I also have gcc48 installed, how can I make clang to refer gcc48 headers?
___
freebsd
Subject: c++11 question: clang++ 3.3 future header not found
% uname -a
FreeBSD cobalt 9.2-RC3 FreeBSD 9.2-RC3 #0 r254795: Sat Aug 24 20:25:04 UTC
2013
r...@bake.isc.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
% clang++ --version
FreeBSD clang version 3.3 (tags/RELEASE_33/final
();
return 0;
}
error received is
% clang++ -otest test.cc
test.cc:2:10: fatal error: 'future' file not found
#include future
^
1 error generated.
I guess clang is re-using system headers which belong to older gcc 4.2
I also have gcc48 installed, how can I make
test.cc:2:10: fatal error: 'future' file not found
#include future
^
1 error generated.
I guess clang is re-using system headers which belong to older gcc 4.2
I also have gcc48 installed, how can I make clang to refer gcc48 headers
- Original Message -
From: Tijl Coosemans t...@coosemans.org
To: Quark unixuser2000-f...@yahoo.com
Cc: freebsd-questions@freebsd.org freebsd-questions@freebsd.org
Sent: Tuesday, 27 August 2013 1:41 PM
Subject: Re: c++11 question: clang++ 3.3 future header not found
On Tue, 27
i'm trying to install 8.4 on a thinkpad x230, which uses a usb cdrom.
according to the hardward docs, 8.4 supports teac cd-210pu. that is what i
am using. the box boots up fine from the installation cd. but when it comes
to choosing an installation medium, the system doesn't find the device.
I was trying to use the content management system for our website. I needed to
restart on terminal but I keep coming up with the following error: I don't
know programing at all, so don't know if this is something I can fix.
Shared object libc.so.6 not found, required by fortune
Neither
.
In worst case, notify your system administrator.
Shared object libc.so.6 not found, required by fortune
This kind of error often indicates an incomplete system update
were libraries are out of date or missing. What way of system
update has been performed?
root@psumc:/usr/local/tomcat5.5 # bin
, but
today I can not use pkg.
today when i put pkg update:
pkg:
ftp://ftp.freebsd.org/pub/FreeBSD/ports/i386/packages-9-stable/Latest//repo.txz:File
unavailable (e.g., file not found, no access)
currently i have:
#~pkg info pkg
pkg-1.0.1 New generation manager
I copy
List,
I installed ``latex`` from packages. That part worked. When using latex
however, it gives me an error::
LaTeX Error: File `utf8x.def' not found.
Where do I get this file? Obviously I'm missing some package of extras or
something. Google reveals linux users solving this problem
On Sun, 20 Jan 2013 19:35:31 -0700, Modulok wrote:
List,
I installed ``latex`` from packages. That part worked. When using latex
however, it gives me an error::
LaTeX Error: File `utf8x.def' not found.
Where do I get this file? Obviously I'm missing some package of extras
In your LaTeX source file, you have \usepackage[utf8x]{inputenc}
somewhere, and you're using UTF-8 characters for whatever reason.
You need to install the port latex-ucs (in the print category)
to make this work. I assume there's also a package for this.
Hmmm. LaTeX is called by sphinx to
On Sun, 20 Jan 2013 23:17:22 -0700, Modulok wrote:
In your LaTeX source file, you have \usepackage[utf8x]{inputenc}
somewhere, and you're using UTF-8 characters for whatever reason.
You need to install the port latex-ucs (in the print category)
to make this work. I assume there's also a
.
Then I:
cd /usr/ports
make print-index
and this is my result:
Generating INDEX-9 - please wait..perl: not found
Makefile, line 31: warning: perl -V:archname returned non-zero status
perl: not found
Done.
O.K., I'm stumped...what's wrong?
Ed
On 28/09/2012 21:27, Ed Flecko wrote:
Generating INDEX-9 - please wait..perl: not found
Makefile, line 31: warning: perl -V:archname returned non-zero status
perl: not found
Done.
O.K., I'm stumped...what's wrong?
You need to install perl in order to build an INDEX from scratch.
That's
8.2-RELEASE FreeBSD 8.2-RELEASE #0
with current portsnap
mtr, postfix-current, pcre all fail to install with error:
** Cannot --enable-pcretest-libedit because libedit library was not found.
=== Script configure failed unexpectedly.
Please report the problem to m...@freebsd.org [maintainer
On 20/05/2012 17:22, Len Conrad wrote:
8.2-RELEASE FreeBSD 8.2-RELEASE #0
with current portsnap
mtr, postfix-current, pcre all fail to install with error:
** Cannot --enable-pcretest-libedit because libedit library was not found.
=== Script configure failed unexpectedly.
Please report
provides the .7 incarnation.
I found a comment (http://forums.freebsd.org/showthread.php?t=21886) that this
library is part of security/openssl but a reinstall just now of openssl only
gave me libssl.so.8, so that's no longer valid. Creating a link to libssl.so.7
fixes the problem but is probably
with
Samba36. Again I'm wondering what version provides the .7
incarnation.
I found a comment (http://forums.freebsd.org/showthread.php?t=21886)
that this library is part of security/openssl but a reinstall just
now
of openssl only gave me libssl.so.8, so that's no longer valid.
Creating a link
-Shared-object-libz-so-5-not-found-tp5662329p5663803.html
Sent from the freebsd-questions mailing list archive at Nabble.com.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any
Hi,
Each fs should have its own lost+found directory.
It is used by fsck for placing recovered corrupted fs files in there.
This implies the dir must have already existed (it may not be mounted ad hoc
e.g. at boot time, during fs recovery).
In FreeBSD 9, I found lost+found dir under /mnt
On Tue, Mar 13, 2012 at 2:58 AM, jb jb.1234a...@gmail.com wrote:
Hi,
Each fs should have its own lost+found directory.
It is used by fsck for placing recovered corrupted fs files in there.
This implies the dir must have already existed (it may not be mounted ad
hoc
e.g. at boot time
On Tue, 13 Mar 2012 07:58:09 + (UTC), jb wrote:
Hi,
Each fs should have its own lost+found directory.
It is used by fsck for placing recovered corrupted fs files in there.
Correct.
This implies the dir must have already existed (it may not be mounted ad hoc
e.g. at boot time, during
jb jb.1234a...@gmail.com wrote:
Hi,
Each fs should have its own lost+found directory.
It is used by fsck for placing recovered corrupted fs files in there.
This implies the dir must have already existed (it may not be mounted ad hoc
e.g. at boot time, during fs recovery).
In FreeBSD 9
On Thu, Feb 16, 2012 at 9:08 AM, Antonio Olivares
olivares14...@gmail.com wrote:
On Thu, Feb 16, 2012 at 8:18 AM, Ryan Frederick
ryanrfreder...@gmail.com wrote:
It looks like others have run into this problem with avahi-app as well:
On Thu, 16 Feb 2012 09:08:54 -0600
Antonio Olivares wrote:
On Thu, Feb 16, 2012 at 8:18 AM, Ryan Frederick
ryanrfreder...@gmail.com wrote:
It looks like others have run into this problem with avahi-app as
well:
http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068658.html
A
(bswap
%0 : +r (__X)); __X; }));' at ';'
/libexec/ld-elf.so.1: Shared object libpcre.so.0 not found, required
by libavahi-glib.so.1
Command
'['/usr/ports/net/avahi-app/work/avahi-0.6.29/avahi-gobject/tmp-introspectGYNEXM/Avahi-0.6',
'--introspect-dump=/usr/ports/net/avahi-app/work/avahi-0.6.29
On Thu, Feb 16, 2012 at 8:18 AM, Ryan Frederick
ryanrfreder...@gmail.com wrote:
It looks like others have run into this problem with avahi-app as well:
http://lists.freebsd.org/pipermail/freebsd-ports/2011-July/068658.html
A cursory search shows that uninstalling avahi-app then reinstalling
Dear folks,
I updated ports and one failed, gimp-app. I checked /usr/src/UPDATING
and I followed advice there to run
# portmaster -w devel/pcre
and I did this, and now machine won't get X. How can I bypass this
mistake? I am now hesitant to update the other machines :(, I will
get into
You can recompile all ports that depend on pcre so that they'll use the
new shared library.
You can do so with:
# portmaster -r pcre-8.30
Ryan
On 02/15/2012 08:42 PM, Antonio Olivares wrote:
Dear folks,
I updated ports and one failed, gimp-app. I checked /usr/src/UPDATING
and I followed
You can recompile all ports that depend on pcre so that they'll use the
new shared library.
You can do so with:
# portmaster -r pcre-8.30
Ryan
On 02/15/2012 08:42 PM, Antonio Olivares wrote:
Dear folks,
I updated ports and one failed, gimp-app. I checked /usr/src/UPDATING
and I
Antonio Olivares olivares14...@gmail.com wrote;
I am doing this and see how it goes. I used ldd to check for
libprce.so and I got :
ldd /usr/local/lib/libprce.so:
libc.so.7 = /lib/libc.so.7 (0x800647000)
ldd /usr/local/lib/libprce.so.1:
libc.so.7 = /lib/libc.so.7
/include/machine/endian.h:130: syntax error, unexpected ';' in '
return (__extension__ ({ register __uint32_t __X = (_x); __asm (bswap
%0 : +r (__X)); __X; }));' at ';'
/libexec/ld-elf.so.1: Shared object libpcre.so.0 not found, required
by libavahi-glib.so.1
Command
'['/usr/ports/net/avahi-app/work
On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller vmil...@hostileadmin.com wrote:
Thanks Rob...
I put the kernel conf file in the source tree as opposed to linking to
it and it certainly did compile the custom kernel.
What confuses me (not that I expect you to have the answer) is that
Chapter 9
Thanks Rob and Lowell,
I will keep this information handy. It was helpful.
On Tue, Jan 31, 2012 at 4:22 AM, Rob Farmer rfar...@predatorlabs.net wrote:
On Mon, Jan 30, 2012 at 10:39 AM, Rick Miller vmil...@hostileadmin.com
wrote:
Thanks Rob...
I put the kernel conf file in the source tree
Thanks Rob...
I put the kernel conf file in the source tree as opposed to linking to
it and it certainly did compile the custom kernel.
What confuses me (not that I expect you to have the answer) is that
Chapter 9 of the handbook has a tip that recommends keeping the kernel
config in
Rick Miller vmil...@hostileadmin.com writes:
Thanks Rob...
I put the kernel conf file in the source tree as opposed to linking to
it and it certainly did compile the custom kernel.
What confuses me (not that I expect you to have the answer) is that
Chapter 9 of the handbook has a tip that
Hi All,
I am performing a `make release` to build a new release with a custom
kernel. The `make release` fails with the following error:
cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64
KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels KODIR=/MYKERNEL
ERROR: Missing kernel
On Sun, Jan 29, 2012 at 9:03 AM, Rick Miller vmil...@hostileadmin.com wrote:
Hi All,
I am performing a `make release` to build a new release with a custom
kernel. The `make release` fails with the following error:
cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64
2012-01-29 18:03, Rick Miller skrev:
Hi All,
I am performing a `make release` to build a new release with a custom
kernel. The `make release` fails with the following error:
cd /usr/src/release/..; make TARGET_ARCH=amd64 TARGET=amd64
KERNCONF=MYKERNEL kernel DESTDIR=/R/stage/kernels
Jasper Valentijn wrote:
L.S.,
I'm not able to install FreeBSD on a Sony Vaio vgn-cr31s. The problem
seems to be related to PR kern/153440,
http://www.freebsd.org/cgi/query-pr.cgi?pr=153440cat=.
The FreeBSD-9.0-RELEASE-i386-memstick.img was used to try the
install and extraction of the
Mike wrote:
I do not have this hardware, so these are just a couple of wild guessses
from the blue on my part. I am also looking only at 64 bit platforms here,
so if there is any signifigant difference with 32 bit I can't look/see.
Just to be on the safe side I've also tried the 9.0 amd64
because of this.
buildkernel, make installkernel and mergemaster -i, and make
installworld and now X does not work, I get error in subject
Shared object libxcb-aux.so.0 not found, required by
libxfsm-4.6.so.0 FreeBSD
any ideas/suggestions for a fix?
Thanks in advance,
Antonio
Found
, make
Correction here. Meant FreeBSD 9.0 not Fedora 9 :(
Message probably ignored because of this.
buildkernel, make installkernel and mergemaster -i, and make
installworld and now X does not work, I get error in subject
Shared object libxcb-aux.so.0 not found, required by
libxfsm-4.6
Even after following said instruction in UPDATING, libxcb-aux.so.0 does
not get installed by any of the XCB ports
#pkg_info |grep -i xcb
libxcb-1.7 The X protocol C-language Binding (XCB) library
xcb-proto-1.6 The X protocol C-language Binding (XCB) protocol
xcb-util-0.3.8,1A
On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com wrote:
Even after following said instruction in UPDATING, libxcb-aux.so.0 does
not get installed by any of the XCB ports
It was replaced with libxcb-util.so.0.
#pkg_info |grep -i xcb
libxcb-1.7 The X protocol
On 01/17/12 15:39, Michael Johnson wrote:
On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com
mailto:jimmie...@gmail.com wrote:
Even after following said instruction in UPDATING, libxcb-aux.so.0
does not get installed by any of the XCB ports
It was replaced with
On Tue, 17 Jan 2012, Jimmie James wrote:
On 01/17/12 15:39, Michael Johnson wrote:
On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com
mailto:jimmie...@gmail.com wrote:
Even after following said instruction in UPDATING, libxcb-aux.so.0
does not get installed by any of
On 01/17/12 16:50, Warren Block wrote:
On Tue, 17 Jan 2012, Jimmie James wrote:
On 01/17/12 15:39, Michael Johnson wrote:
On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com
mailto:jimmie...@gmail.com wrote:
Even after following said instruction in UPDATING, libxcb-aux.so.0
On 01/17/12 16:50, Warren Block wrote:
On Tue, 17 Jan 2012, Jimmie James wrote:
On 01/17/12 15:39, Michael Johnson wrote:
On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com
mailto:jimmie...@gmail.com wrote:
Even after following said instruction in UPDATING, libxcb-aux.so.0
On 01/17/12 16:50, Warren Block wrote:
On Tue, 17 Jan 2012, Jimmie James wrote:
On 01/17/12 15:39, Michael Johnson wrote:
On Tue, Jan 17, 2012 at 3:04 PM, Jimmie James jimmie...@gmail.com
mailto:jimmie...@gmail.com wrote:
Even after following said instruction in UPDATING, libxcb-aux.so.0
Sorry for top posting in this message, but one reboot and a ldconfig -R
allows everything to be rebuilt.
Not sure which was the key here, but for others, I'd try ldconfig -R
first. Not sure why portupgrade and portmaster failed though.
On 01/18/12 00:11, Jimmie James wrote:
On 01/17/12 16:50,
does not work, I get error in subject
Shared object libxcb-aux.so.0 not found, required by
libxfsm-4.6.so.0 FreeBSD
any ideas/suggestions for a fix?
Thanks in advance,
Antonio
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org
)
fdisk: invalid fdisk partition table found
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 63, size 33045642 (16135 Meg), flag 80 (active)
beg
to be used for BIOS calculations are:
cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl)
fdisk: invalid fdisk partition table found
[robert@dell64] ~ sudo gpart destroy da1
Password:
gpart: Device busy
gpart won't destroy a GEOM unless it's unused. So either delete all the
partitions
On Mon, 28 Nov 2011 08:02:55 -0700 (MST)
Warren Block wbl...@wonkity.com wrote:
On Mon, 28 Nov 2011, Robert wrote:
Thanks for hanging in there with me. I am about ready to give up,
but here is where everything stands now.
Before giving up, a few more suggestions. First, check the BIOS
On Mon, 28 Nov 2011, Robert wrote:
I did discover that an external card reader I was using on the Windows
XP computer is defective. It had a bent pin and another recessed pin.
I hope that is not what damaged these cards.
Ouch. That sounds like a logical cause. Although the card itself has
partition table found. Rather than starting with an invalid table,
it created a valid default table in memory.
Do both cards report the same size?
Yes..sort of 28, 29 MB
Some difference today. Not sure at what point this happened but one of
my CF cards now reads:
[robert@dell64] ~ fdisk
=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=2057 heads=255 sectors/track=63 (16065 blks/cyl)
fdisk: invalid fdisk partition table found
Media sector size is 512
Warning: BIOS sector numbering starts
of the HD.
http://wiki.freenas.org/faq:0129
Then follow instructions found here.
http://forums.freebsd.org/showthread.php?t=13780
This will leave you with fat32 format on your md cards. Then insert into
ms/windows system and use windows explorer to select the drive letter of
the md card, right
heads=255 sectors/track=63 (16065 blks/cyl)
Figures below won't work with BIOS for partitions not in cyl 1
parameters to be used for BIOS calculations are:
cylinders=2057 heads=255 sectors/track=63 (16065 blks/cyl)
fdisk: invalid fdisk partition table found
Media sector size is 512
Warning: BIOS
sectors/track=32 (2048 blks/cyl)
fdisk: invalid fdisk partition table found
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 32, size 59360 (28 Meg), flag
disklabel are:
cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl)
parameters to be used for BIOS calculations are:
cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl)
fdisk: invalid fdisk partition table found
The partition table was cleared.
Media sector size is 512
***
parameters extracted from in-core disklabel are:
cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl)
parameters to be used for BIOS calculations are:
cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl)
fdisk: invalid fdisk partition table found
The partition table was cleared.
Media sector
found
Message-ID: 2023192154.5b0a64ab@dell64
In-Reply-To: 20232108.panl80g3041...@fire.js.berklix.net
References: 2023123347.4f439c9c@dell64
20232108.panl80g3041...@fire.js.berklix.net
X-Mailer: Claws Mail 3.7.10 (GTK+ 2.24.6; amd64-portbld-freebsd8.2)
Mime-Version: 1.0
/cyl)
fdisk: invalid fdisk partition table found
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 32, size 59360 (28 Meg), flag 80 (active)
beg: cyl
to be used for BIOS calculations are:
cylinders=29 heads=64 sectors/track=32 (2048 blks/cyl)
fdisk: invalid fdisk partition table found
The partition table was cleared.
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition
partition table found
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 32, size 59360 (28 Meg), flag 80 (active)
beg: cyl 0/ head 1/ sector 1
blks/cyl)
fdisk: invalid fdisk partition table found
Media sector size is 512
Warning: BIOS sector numbering starts with sector 1
Information from DOS bootblock is:
The data for partition 1 is:
sysid 165 (0xa5),(FreeBSD/NetBSD/386BSD)
start 32, size 59360 (28 Meg), flag 80 (active
It looks like I never got round to sending in a send-pr for that, so feel free
looks like its been that way at least since 7.1.see
http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/gen/sbin/fdisk/
I thought I had seen a mention of that somewhere, so I grep'ed the man
pages. I found hints on geom(4
since 7.1.see
http://berklix.com/~jhs/src/bsd/fixes/FreeBSD/src/gen/sbin/fdisk/
I thought I had seen a mention of that somewhere, so I grep'ed the man
pages. I found hints on geom(4) and boot0cfg(8), but they certainly
aren't obvious.
Yup, bit me too long ago, presumably from my patch, bit
On Wed, 23 Nov 2011, Julian H. Stacey wrote:
2 Base of _my_ man fdisk
When running multi user, you cannot write unless you first run this:
sysctl kern.geom.debugflags=16
But that's not quite correct. Setting debugflags to 16 allows writes to
a partition that's mounted, something
Just noticed that I did not include questions@. It has been a long day.
Begin forwarded message:
Date: Wed, 23 Nov 2011 19:21:54 -0800
From: Robert travelin...@cox.net
To: Julian H. Stacey j...@berklix.com
Subject: Re: Invalid fdisk partition table found
Julian and Warren thanks
On Wed, 2 Nov 2011 17:15:56 -0300
Zantgo zan...@gmail.com wrote:
I install slim and xfce4, and I put slim in the boot,
What do you mean exactly, put slim in the boot???
when the system booting, everything works fine when login screen
appears I can not type slim or move the mouse, which is
On Wed, 2 Nov 2011 17:15:56 -0300
Zantgo zan...@gmail.com wrote:
I install slim and xfce4, and I put slim in the boot, when the system
booting, everything works fine when login screen appears I can not
type slim or move the mouse, which is the problem?
Here's a link you *really* should read.
I install slim and xfce4, and I put slim in the boot, when the system booting,
everything works fine when login screen appears I can not type slim or move the
mouse, which is the problem?
___
freebsd-questions@freebsd.org mailing list
On Wed, 2 Nov 2011 17:15:56 -0300
Zantgo zan...@gmail.com wrote:
I install slim and xfce4, and I put slim in the boot, when the system
booting, everything works fine when login screen appears I can not
type slim or move the mouse, which is the problem?
My prime suspect would dbus not running.
El 02-11-2011, a las 17:48, Christopher J. Ruwe c...@cruwe.de escribió:
On Wed, 2 Nov 2011 17:15:56 -0300
Zantgo zan...@gmail.com wrote:
I install slim and xfce4, and I put slim in the boot, when the system
booting, everything works fine when login screen appears I can not
type slim or
On Wed, 02 Nov 2011 15:55:47 -0500, zan...@gmail.com wrote:
But in my rc.conf said dbus_enable=YES
and HAL? Your Xorg was probably compiled with HAL. I've had this problem
before though and the fix was to recompile X without HAL. Sucks to not be
able to plugplay though.
El 02-11-2011, a las 18:19, Mark Felder f...@feld.me escribió:
On Wed, 02 Nov 2011 15:55:47 -0500, zan...@gmail.com wrote:
But in my rc.conf said dbus_enable=YES
and HAL? Your Xorg was probably compiled with HAL. I've had this problem
before though and the fix was to recompile X
2011/11/2, Zantgo zan...@gmail.com:
I install slim and xfce4, and I put slim in the boot, when the system
booting, everything works fine when login screen appears I can not type slim
or move the mouse, which is the problem?
Did you read about xorg in handbook?, did you read the message when
grullahighschool# portmaster -a
=== License check disabled, port has not defined LICENSE
=== Found saved configuration for ca_root_nss-3.12.9
= nss-3.12.11.with.ckbi.1.87.tar.gz doesn't seem to exist in
/usr/ports/distfiles//.
= Attempting to fetch
http://ftp.mozilla.org/pub/mozilla.org
version available: gtk-update-icon-cache-2.24.6
=== New version available: firefox-6.0.1,1
=== 402 total installed ports
=== 4 have new versions available
grullahighschool# portmaster -a
=== License check disabled, port has not defined LICENSE
=== Found saved configuration
not defined LICENSE
=== Found saved configuration for ca_root_nss-3.12.9
= nss-3.12.11.with.ckbi.1.87.tar.gz doesn't seem to exist in
/usr/ports/distfiles//.
= Attempting to fetch
http://ftp.mozilla.org/pub/mozilla.org/security/nss/releases/NSS_3_12_11_WITH_CKBI_1_87_RTM/src/nss-3.12.11.with.ckbi
failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript
... but then I run into the very
same failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not
found -- snapshot corrupt.
I've been looking at the portsnap
/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is
generated
by the shell's built-in test command, specifically '[ -r'. It is looking
for a
file that was extracted with tar. So the place to look for the bug is IMO
1
to use 'extract'. I do ... but then I run into the very
same failure:
(portsnap fetch extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
not
found
/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is
generated
by the shell's built-in test command, specifically '[ -r'. It is looking
for a
file that was extracted with tar. So the place to look for the bug
/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is
generated
by the shell's built-in test command, specifically '[ -r
On Sat, Aug 13, 2011 at 12:43:52AM +0200, Hartmann, O. wrote:
On 08/12/11 22:54, Roland Smith wrote:
On Fri, Aug 12, 2011 at 08:44:07PM +0200, Hartmann, O. wrote:
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz
Does this file actually exist if you extract the
/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not
found -- snapshot corrupt.
Oliver
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe
extract:)
/usr/ports/devel//
/usr/ports/devel/ccdoc/
/usr/ports/devel/ccrtp/
/usr/ports/devel/cdash/
files/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not
found -- snapshot corrupt.
I've been looking at the portsnap shellscript. This error message is generated
/dd7c394c9c9ddf4b97f1b14c676f370adc259b2c7a4b8346eba0788a431db398.gz not
found -- snapshot corrupt.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions
1 - 100 of 1223 matches
Mail list logo
